From: Petr Vorel <petr.vorel@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] package/iputils: fix IPUTILS_PERMISSIONS
Date: Tue, 18 Jun 2019 09:01:52 +0200 [thread overview]
Message-ID: <20190618070151.GD8350@x230> (raw)
In-Reply-To: <20190618084948.0a451f1b@windsurf>
Hi Thomas,
> Hello,
> On Mon, 17 Jun 2019 22:32:36 +0200
> Petr Vorel <petr.vorel@gmail.com> wrote:
> > The only thing to consider:
> > Upstream doesn't care much about systems without usr merge.
> > I wonder if systems without it (unset BR2_ROOTFS_MERGED_USR),
> > whether we want to have /bin/ping and symlinked it into /usr/bin/ping.
> > I see this is handled for coreutils (COREUTILS_BIN_PROGS).
> What COREUTILS_CLEANUP_BIN is doing is not to install a symlink
> between /bin/foo and /usr/bin/foo. Indeed, such a symlink is not
> necessary: both /bin and /usr/bin are in the PATH, so having /bin/foo
> and /usr/bin/foo is totally useless.
> What COREUTILS_CLEANUP_BIN does is to make sure that in a
> non-BR2_ROOTFS_MERGED_USR case, the symlinks to coreutils are installed
> in the same location as the corresponding Busybox applets, so that we
> properly handle the conflict between Busybox applets and full-blown
> variants, as I explained in my reply to your comments on PATCH 1/2.
Thanks for an explanation.
Kind regards,
Petr
> Best regards,
> Thomas
next prev parent reply other threads:[~2019-06-18 7:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-16 20:09 [Buildroot] [PATCH 1/2] package/iputils: move binaries to the location also used by Busybox Thomas Petazzoni
2019-06-16 20:09 ` [Buildroot] [PATCH 2/2] package/iputils: fix IPUTILS_PERMISSIONS Thomas Petazzoni
2019-06-17 20:32 ` Petr Vorel
2019-06-18 6:49 ` Thomas Petazzoni
2019-06-18 7:01 ` Petr Vorel [this message]
2019-06-16 20:20 ` [Buildroot] [PATCH 1/2] package/iputils: move binaries to the location also used by Busybox Yann E. MORIN
2019-06-17 17:31 ` Thomas Petazzoni
2019-06-17 20:24 ` Petr Vorel
2019-06-18 6:46 ` Thomas Petazzoni
2019-06-18 6:59 ` Petr Vorel
2019-06-18 7:17 ` Thomas Petazzoni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190618070151.GD8350@x230 \
--to=petr.vorel@gmail.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox