[Buildroot] [PATCH] system: add options for /bin /sbin and /lib to be symlinks into /usr

Mike Williams mike at mikebwilliams.com
Wed Sep 2 13:50:34 UTC 2015


On Wed, Sep 2, 2015 at 3:10 AM, Thomas Petazzoni <
thomas.petazzoni at free-electrons.com> wrote:

> Dear Yann E. MORIN,
>
> On Wed,  2 Sep 2015 00:55:13 +0200, Yann E. MORIN wrote:
> > systemd is incresaingly expected things to live in /usr/bin or
> > /usr/sbin.
> >
> > However, a lot of packages stil install stuff directly into /bin or
> > /sbin.
> >
> > Add an option so that /bin and /sbin be symlinks to /usr/bin and
> > /usr/sbin. Ditto for .lib for consistency.
> >
> > That option is forcibly enabled when the init system is systemd.
> >
> > Signed-off-by: "Yann E. MORIN" <yann.morin.1998 at free.fr>
>
> But do we actually need this? Vicente sent a patch to fix the systemd
> issues that were discussed on the list:
>
>    [PATCH] systemd: override the path for kill, sulogin, mount and umount
>

It's not just what systemd expects, many packages by default install their
systemd-related items to /lib, etc. instead of /usr/lib, so we either have
manual fixes to the .mk files for those packages or inconsistencies in
where those items go. As an example, I believe rsyslog is passed a special
flag setting its systemd install location to /usr/lib, and gpsd is still
just installing to /lib/systemd/system.

It wouldn't surprise me if most of our systemd users had already merged
their directories in their skeleton; I will probably do so soon as well.

Mike
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150902/aa8dc4b1/attachment-0002.html>


More information about the buildroot mailing list