Re: [gentoo-dev] Re: New SYMLINK_LIB=no migration tool for review

["Michał Górny" <mgorny@gentoo.org>]

[-- Attachment #1: Type: text/plain, Size: 1406 bytes --]

On śro, 2017-08-02 at 21:02 -0400, Walter Dnes wrote:
> On Wed, Aug 02, 2017 at 03:25:01PM -0400, Mike Gilbert wrote
> > On Wed, Aug 2, 2017 at 3:07 PM, Martin Vaeth <martin@mvath.de> wrote:
> > > Mike Gilbert <floppym@gentoo.org> wrote:
> > > > On Wed, Aug 2, 2017 at 1:51 PM, Martin Vaeth <martin@mvath.de> wrote:
> > > > > If this already was discussed then sorry for the noise:
> > > > > 
> > > > > What is the rationale for merging lib32 with lib?
> > > > > Wouldn't it be somewhat cleaner to have a completely
> > > > > split structure
> > > > > 
> > > > > lib64
> > > > > lib32
> > > > > libx32 (possibly)
> > > > > lib
> > > > 
> > > > Here are a couple of reasons:
> > > > 
> > > > 1. Other distros (notably Red Hat and Fedora) put 32-bit libs in "lib".
> > > 
> > > According to bug 506276, Debian has instead merged 64-bit to lib.
> > > So it seems to me that there is no "mainstream" to follow.
> > > Perhaps striving for the cleanest solution would be the best?
> > 
> > Debian puts 64-bit libs in /lib/(host), where (host) is something like
> > x86_64-linux-gnu. They don't get put in /lib directly. They call this
> > "multiarch".
> > 
> > Migrating Gentoo to a "multiarch" config is a larger project.
> 
>   And what happens when 128-bit cpus debut? /lib128?

Then we use whatever path is used in the appropriate ABI.

-- 
Best regards,
Michał Górny

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 988 bytes --]