[Buildroot] [PATCH] procps-ng: remove the remaining busybox symlinks
Vicente Olivert Riera
Vincent.Riera at imgtec.com
Wed Jan 13 15:26:42 UTC 2016
Hello Peter, Thomas, Yann,
On 12/01/16 20:42, Peter Korsgaard wrote:
>>>>>> "Yann" == Yann E MORIN <yann.morin.1998 at 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.
More information about the buildroot
mailing list