[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Moving 32-bit libraries to (/usr)/lib32 on amd64

Steve Langasek a écrit :
On Mon, Feb 20, 2006 at 11:10:41AM -0700, Bdale Garbee wrote:

On Mon, 2006-02-20 at 02:23 -0800, Steve Langasek wrote:

If there's
consensus that putting this stuff in /usr/lib32 on amd64 is prettier than
/emul/ia32-linux, I see no reason not to move forward.

My sense is that the "concensus" that exists is around FHS compliance.
While I personally consider /usr/lib32 pretty ugly, I am sensitive to
the fact that we have always tried to be FHS compliant in Debian.

 /lib64 and /lib32 : 64/32-bit libraries (architecture dependent)

 The 64-bit architectures PPC64, s390x, sparc64 and AMD64 must place 64-bit
 libraries in /lib64, and 32-bit (or 31-bit on s390) libraries in /lib.

 The 64-bit architecture IA64 must place 64-bit libraries in /lib.


So there really is no way to comply with the current FHS on amd64 without
some serious package special-casing.  That makes /emul/ia32-linux vs.
/usr/lib32 entirely a question of aesthetics, not standards-compliance.

Moving 32-bit libraries to (/usr)/lib32 won't make the amd64 port compliant with the FHS, which is almost impossible given the current setup, ie 64-bit libraries in /lib. However, it would make it compliant with the part of the FHS which says that alternative libraries have to be in (/usr)/lib<qual>. And it would make us compatible with other distributions like Gentoo or Ubuntu that have choosen to use (/usr)/lib32.

  .''`.  Aurelien Jarno	            | GPG: 1024D/F1BCDB73
 : :' :  Debian GNU/Linux developer | Electrical Engineer
 `. `'   aurel32@debian.org         | aurelien@aurel32.net
   `-    people.debian.org/~aurel32 | www.aurel32.net

Reply to: