Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] procps-ng: remove the remaining busybox symlinks
Date: Wed, 13 Jan 2016 15:26:42 +0000	[thread overview]
Message-ID: <56966CB2.5030702@imgtec.com> (raw)
In-Reply-To: <8760yy8r7b.fsf@dell.be.48ers.dk>

Hello Peter, Thomas, Yann,

On 12/01/16 20:42, Peter Korsgaard wrote:
>>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
> 
> Hi,
> 
>  >> I don't think we're doing it this way for any other package. In
>  >> general, we either:
>  >> 
>  >> * Arrange for the package to install its tools at the same location as
>  >> Busybox installs them.
>  >> 
>  >> * Or add a post-install hook to move the binaries installed by the
>  >> package to where Busybox installs them.
>  >> 
>  >> Peter, Yann ?
> 
>  > Yes, I agree with Thomas. First solution is preferred if possible, of
>  > course, so that we don't have to maintain the list of executables to
>  > move in the post-install hook.
> 
> Agreed. If you need to go for the second option make sure it is only
> done if !BR2_ROOTFS_MERGED_USR.
> 

configuring procps-ng for installing its binaries in /bin and /sbin
(first option suggested by Thomas) mostly works, except for two tools
(pidof and watch) which are installed in /usr/bin and their busybox
counterparts still exist in /bin.

configuring procps-ng for installing its binaries in /bin and /sbin
doesn't mean that all its binaries will end up in /bin and /sbin. Some
of them are still installed in /usr/bin and /usr/sbin.

So, I see three options here:

1 - follow the second suggestion from Thomas (post-install hook to move
the ALL binaries installed by the package to where Busybox installs them)

2 - same thing but only move pidof and watch binaries

3 - remove /bin/pidof and /bin/watch symlinks installed by Busybox

I happy with any of them, so, which one do you prefer?

Regards,

Vincent.

  reply	other threads:[~2016-01-13 15:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-12 14:23 [Buildroot] [PATCH] procps-ng: remove the remaining busybox symlinks Vicente Olivert Riera
2016-01-12 20:12 ` Thomas Petazzoni
2016-01-12 20:20   ` Yann E. MORIN
2016-01-12 20:42     ` Peter Korsgaard
2016-01-13 15:26       ` Vicente Olivert Riera [this message]
2016-01-13 15:33         ` Thomas Petazzoni
2016-01-13 15:42           ` Peter Korsgaard

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=56966CB2.5030702@imgtec.com \
    --to=vincent.riera@imgtec.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