>>> Subject: [lfs-dev] Removing /lib64 symlink and /usr/lib64 revisited >>> >>> Okay, now that 7.10 has released, time to bring this up again. >> > Let's put it the other way around. Upstream do a lot of things we may or may > not agree with > (e.g. making gnome systemd only, or making c++14 the default for C++ code in > GCC, etc). > Gnome-3.16.x and 3.21.x work fine on non-systemd for me.
> The question is then: what is the reason to depart from upstream will about > lib vs lib64? > At a time, the answer was: because not all packages were able to cope with > it, and the symlink > was there to avoid a big mess. Now, this is not true anymore. We may have > other reasons > to keep the symlink, though, but not that one. > After I got gcc/glibc sorted out to work without /lib64, /usr/lib64, /usr/local/lib64, out of many, many packages, only a couple needed some kind of lib64 to be present and then it could be removed after installation. The only things that need lib64 are closed source packages like skype, etc. -- http://lists.linuxfromscratch.org/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
