From: Martin Vaeth <martin@mvath.de>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: New SYMLINK_LIB=no migration tool for review
Date: Thu, 3 Aug 2017 07:50:09 +0000 (UTC) [thread overview]
Message-ID: <slrnoo5ldn.jv8.martin@lounge.imp.fu-berlin.de> (raw)
In-Reply-To: CAJ0EP42jZo8-GzkWuGj-55P1Yg-6Yfu3QE8MqRaX=mQzwA_etw@mail.gmail.com
Mike Gilbert <floppym@gentoo.org> wrote:
> Debian puts 64-bit libs in /lib/(host)
Yes, this is somewhat weird:
They have /lib/i386-linux-gnu/ and /lib/x86_64-linux-gnu/
but anyway they use /lib32 instead of e.g. /lib/i686-linux-gnu/
Their reasons for this are mysterious to me.
> Migrating Gentoo to a "multiarch" config is a larger project.
Migrating to the completely split setting /lib{,32,64,x32}
would be _less_ intrusive than to simultaneously omitting /lib32:
With a slight modification of Michał's tool (in the instructions
and keeping lib32 untouched) not even a re-emerge of anything
would be necessary (as is the case now).
This is one of the reasons why a completely split layout appears
safer to me than to combine it with yet another new merge we
have no experience with.
next prev parent reply other threads:[~2017-08-03 7:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-02 15:58 [gentoo-dev] New SYMLINK_LIB=no migration tool for review Michał Górny
2017-08-02 17:51 ` [gentoo-dev] " Martin Vaeth
2017-08-02 18:10 ` Mike Gilbert
2017-08-02 19:07 ` Martin Vaeth
2017-08-02 19:25 ` Mike Gilbert
2017-08-03 1:02 ` Walter Dnes
2017-08-03 2:09 ` Benda Xu
2017-08-03 6:55 ` Michał Górny
2017-08-03 7:23 ` Martin Vaeth
2017-08-03 7:50 ` Martin Vaeth [this message]
2017-08-03 7:57 ` Michał Górny
2017-08-03 14:30 ` Martin Vaeth
2017-08-02 19:44 ` Michał Górny
2017-08-02 18:10 ` Holger Hoffstätte
2017-08-11 23:56 ` [gentoo-dev] " Gerogy Yakovlev
2017-08-12 7:12 ` Michał Górny
2017-08-12 21:33 ` Michał Górny
2017-08-19 22:25 ` Georgy Yakovlev
2017-08-19 22:50 ` Michał Górny
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=slrnoo5ldn.jv8.martin@lounge.imp.fu-berlin.de \
--to=martin@mvath.de \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox