On Sat, Feb 10, 2018 at 12:15:43PM -0600, William Hubbs wrote: > On Sat, Feb 10, 2018 at 03:34:51PM +0000, Duncan wrote: > > William Hubbs posted on Thu, 08 Feb 2018 13:52:56 -0600 as excerpted: > > *snip* > > > > The second change is that baselayout is taking ownership of most of the > > > directories it creates. This includes all directories in / and /usr > > > excluding /lib* and /usr/lib*. Once we drop support for SYMLINK_LIB, > > > baselayout will take ownership of /lib* and /usr/lib* as well. > > > > What's the effect if the "directory" is a symlink to elsewhere? > > When we try to replace the symlink with a directory, the emerge will > fail.
It looks like this isn't quite correct, portage doesn't fail to emerge the package, but it doesn't replace the symlink with the directory either. You may be ok, but you'll have to test. This is all very custom (Gentoo makes these things as directories when the stages are built, so it won't be an issue for a default installation). > > Here, the following system "directories" are actually symlinks: > > > > # makes installing grub to multiple devices much easier > > /boot -> /bt > > > > # "reverse" usrmerge > > /usr -> . > > > > # would be /usr/games, but with reverse usrmerge... > > /game -> . > > > > # shorter path > > /home -> h > > > > # lib(64) merge (including /usr/lib(64) > > /lib -> lib64 > > When we get rid of symlink_lib, we will expect both of these (/lib and > /lib64) to be directories. Mgorny can explain more about this, but > linking lib to lib64 is basically a hack. > > > > > > # would be /usr/local, /l is so much shorter > > /local -> l > > > > # (s)bin merge (including /usr/(s)bin) > > /sbin -> bin > > This will be taken care of in the usr merge support. > > > > > # shouldn't appear on a desktop/workstation system, but bugs... > > /srv -> tmp > > Keep in mind that /tmp is wiped during a reboot, so /srv should be > separate from /tmp. > > > > > # shorter log path (/lg as /l already taken by local) > > /var/log -> /lg > > > > > Third is the beginning of support for the /usr merge through the > > > addition of the usrmerge use flag. > > > DO NOT, DO NOT TURN THIS ON UNLESS YOU KNOW WHAT YOU ARE DOING AND CAN > > > HELP WITH TESTING. > > > > What about "reverse" usrmerge as above? Flag on or not? Maybe I just > > turn it on (obviously after updating my backups) to help test? > > The "reverse" usr merge as you call it is a highly custom configuration; > I do not see us building it into baselayout. However, like I said above, > the baselayout changes will not stop you from configuring this using a > combination of /etc/portage/package.env and /etc/portage/env/baselayout. > > William >
signature.asc
Description: Digital signature
