From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] procps-ng: remove the remaining busybox symlinks
Date: Wed, 13 Jan 2016 16:33:08 +0100 [thread overview]
Message-ID: <20160113163308.03661753@free-electrons.com> (raw)
In-Reply-To: <56966CB2.5030702@imgtec.com>
Vicente,
On Wed, 13 Jan 2016 15:26:42 +0000, Vicente Olivert Riera wrote:
> 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?
I think my personal preference would be to install as many procps-ng
tools as possible in the "right" place, and then only move the few ones
for which you can't configure the installation location.
On a side note, it would be interesting to write a tool that looks if
there are two binaries in bin/, sbin/, usr/bin/ and usr/sbin/ with the
same name, in order to automatically detect at the end of the build if
we have two commands (one full implementation and one from Busybox)
that are installed in different locations.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-01-13 15:33 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
2016-01-13 15:33 ` Thomas Petazzoni [this message]
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=20160113163308.03661753@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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