Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] procps-ng: remove the remaining busybox symlinks
Date: Tue, 12 Jan 2016 21:20:45 +0100	[thread overview]
Message-ID: <20160112202045.GA3463@free.fr> (raw)
In-Reply-To: <20160112211220.2b7c24bb@free-electrons.com>

Thomas, Vicente, All,

On 2016-01-12 21:12 +0100, Thomas Petazzoni spake thusly:
> On Tue, 12 Jan 2016 14:23:01 +0000, Vicente Olivert Riera wrote:
> > procps-ng is installed after busybox to ensure that its tools overwrite
> > the ones installed by busybox. However, some busybox symlinks for tools
> > which are now provided by procps-ng remain in /bin and /sbin pointing to
> > the busybox binary.
> > 
> > This shouldn't be a problem since the /usr/bin directory is listed
> > before /bin in the $PATH variable. However there could be some scripts
> > out there hardcoding the path of those tools calling them by "/bin/ps"
> > for instance.
> > 
> > So in order to avoid potential problems we just remove all busybox
> > symlinks for the tools which are now provided by procps-ng.
> > 
> > Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
[--SNIP--]
> 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.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2016-01-12 20:20 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 [this message]
2016-01-12 20:42     ` Peter Korsgaard
2016-01-13 15:26       ` Vicente Olivert Riera
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=20160112202045.GA3463@free.fr \
    --to=yann.morin.1998@free.fr \
    --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