On Sat, 10 Oct 2015 17:48:15 -0500 William Hubbs <[email protected]> wrote:
> All, > > fhs 3.0 was approved in June this year [1] [2]. > > The piece of it that I want to bring up is the lib and libxx > directories, both in / and /usr. The way I read the fhs, /lib and > /usr/lib should hold the files for the default abi and /libxx and > /usr/libxx should hold the files for the alternate abis. In earlier > fhs, there was an exception for amd64 which stated that the default > libraries should be in /lib64 and /usr/lib64. However, that exception > is now gone. > > I know there was discussion/work in the past on removing the > lib->lib64 symlinks on amd64, but I don't remember what happened to > that discussion. So, I would like to bring it up again and get the > info. > > What would it take for us to remove the lib->lib64 links? > > What would it take for us to do this migration on live systems? I did this for amd64-fbsd, close to its beginning in gentoo; it's a pain for users: it basically sums up to 'set SYMLINK_LIB=no, rm lib, mv lib64 lib, ln -s lib lib64, emerge -e world, rm lib64' ( see https://wiki.gentoo.org/wiki/Gentoo_FreeBSD#All_commands_is_not_working_after_emerge_sys-apps.2Fbaselayout ) emerge -e world was there to kill every hardcoded lib64 in binaries vapier has been working on this afaik ( https://bugs.gentoo.org/show_bug.cgi?id=506276 ), so maybe there is a better solution, but since this changes econf args and get_libdir ouput, I'm not sure 'emerge -e world' can be avoided... Alexis.
