When using the unstable baselayout version without split-usr, it remove all sbin directories from PATH. The comment says they are redundant symlinks with UsrMerge, but UsrMerge refers to bin and sbin as separate directories (see link), and they are not symlinks on other UsrMerge distros. I did not symlink sbin to bin to be consistent with this, so the PATH changes result in many commands not being found. I think these lines should be dropped: https://github.com/gentoo/gentoo/blob/master/sys-apps/baselayout/baselayout-2.7.ebuild#L194-L195 Reproducible: Always Steps to Reproduce: 1. ACCEPT_KEYWORDS=~* emerge -v baselayout 2. grep ^PATH /etc/env.d/50baselayout
https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b4e246839d42a3c9a839801759c20f69c27df964
Notice that https://gitweb.gentoo.org/proj/baselayout.git/tree/Makefile#n97 does that already.
Those links do not get packaged unless USE=build is set, which I don't use. # emerge --{,sys}root=/tmp/newroot =sys-apps/baselayout-2.7 # find /tmp/newroot -type d /tmp/newroot /tmp/newroot/run /tmp/newroot/etc /tmp/newroot/etc/modprobe.d /tmp/newroot/etc/sysctl.d /tmp/newroot/etc/env.d /tmp/newroot/usr /tmp/newroot/usr/share /tmp/newroot/usr/share/baselayout /tmp/newroot/usr/share/doc /tmp/newroot/usr/share/doc/baselayout-2.7 /tmp/newroot/var /tmp/newroot/var/db /tmp/newroot/var/db/pkg /tmp/newroot/var/db/pkg/sys-apps /tmp/newroot/var/db/pkg/sys-apps/baselayout-2.7 /tmp/newroot/var/cache /tmp/newroot/var/cache/edb /tmp/newroot/var/lib /tmp/newroot/var/lib/portage /tmp/newroot/var/tmp /tmp/newroot/tmp
William should pitch in, but the rationale for merging bin and sbin dirs was given in https://lists.fedoraproject.org/pipermail/devel/2011-October/158845.html I don't see a point in adding another USE=split-bin that allows for merged-/usr-but-split-bin/-and-sbin/. The separation between bin/ and sbin/ is mostly pointless.
Interesting that it was proposed on the Fedora list, and they still have separate bin and sbin a decade later. It seems everything based on Fedora/RHEL and Ubuntu keeps them separate, but I see Arch links sbin to bin. But okay, if the split bin/sbin layout is intended to be unsupported in Gentoo, then I'll rewrite my layout to copy Arch.
(In reply to David Michael from comment #5) > Interesting that it was proposed on the Fedora list, and they still have > separate bin and sbin a decade later. It seems everything based on > Fedora/RHEL and Ubuntu keeps them separate, but I see Arch links sbin to bin. > > But okay, if the split bin/sbin layout is intended to be unsupported in > Gentoo, then I'll rewrite my layout to copy Arch. One of the main reasons of USE=-split-usr being package.use.force'd: How would you even change this? Move /usr/sbin/* stuff to /usr/bin/ in pkg_postinst, and then tell the user to re-emerge his world? USE=-split-usr is extremely hairy (and I've shot myself in the foot multiple times with it). That said, we should clearly document this better for those willing to go to a fully-merged system.
Yeah, I'm not suggesting unmasking the flag; that's clearly a problem. My systems cross-build the entire file system image from scratch in one shot, so the setting is not an issue for me.
Here is more information about the issues involved in this bug [1]. Given the link above and this one, I do not understand the value of having sbin split from bin. If someone can convince me that doing so has value, I am willing to re-consider this position. Let me know what you think. [1] https://www.osnews.com/story/25556/understanding-the-bin-sbin-usrbin-usrsbin-split/
This can just be closed if there is nothing to be done (docs), since combining bin and sbin was intentional. I opened the bug because the PATH is broken when upgrading baselayout, which references UsrMerge as the reason, which is unrelated to combining bin and sbin so it looked unintentional. I've already changed my systems' layout over a week ago to use this Arch-like layout instead, so they're working again.
*** Bug 793761 has been marked as a duplicate of this bug. ***
