From: "Holger Hoffstätte" <holger@applied-asynchrony.com>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: New SYMLINK_LIB=no migration tool for review
Date: Wed, 2 Aug 2017 18:10:32 +0000 (UTC) [thread overview]
Message-ID: <pan$e213f$12847e83$45dd1231$2d08cff1@applied-asynchrony.com> (raw)
In-Reply-To: slrnoo449l.28u.martin@lounge.imp.fu-berlin.de
On Wed, 02 Aug 2017 17:51:43 +0000, Martin Vaeth wrote:
> Michał Górny <mgorny@gentoo.org> wrote:
>>
>> What are your thoughts?
>
> 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
I wondered the same. If anything it would make more sense to merge
lib64 into lib, since it's the platform's default (assuming 64bit).
Merging lib32 into lib is going to cause nothing but problems.
-h
next prev parent reply other threads:[~2017-08-02 18:11 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
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 [this message]
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='pan$e213f$12847e83$45dd1231$2d08cff1@applied-asynchrony.com' \
--to=holger@applied-asynchrony.com \
--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