i dont care what the FHS has to say on the topic, so i havent bothered looking. below is documentation on the current system, and where i plan on taking things in the future.
note that this only applies to amd64, ppc64, sparc64, and s390x systems where people think in terms of "32bit" and "64bit" ABIs (even though our ABI system isn't restricted at all to just these two states). all current multilib systems use the sub-profile features/multilib/lib32/. in there, we set SYMLINK_LIB=yes. this causes the 32bit libs to move from their normal ABI location in "lib" to "lib32" and then symlink "lib" to "lib64". this is the only currently supported setup, but can be considered legacy. in the future, multilib profiles we'll be moving to SYMLINK_LIB=no and using just features/multilib/. so there will be no "lib32" dir at all, "lib" will be for 32bit libs (just like the matching 32bit arch), and "lib64" will be for 64bit libs. as for no-multilib systems, "lib64" will be the same, and "lib" will be symlinked to "lib64". this will be easier i think to share files between multilib and non-multilib 64bit systems. -mike
signature.asc
Description: This is a digitally signed message part.
