From: Skirmisher <Skirmisher@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [RFC/tracking issue] deprecating -lib32 multilib system
Date: Tue, 22 Dec 2020 02:22:54 +0100 [thread overview]
Message-ID: <20201222012254.H9F97Y3YIqxZu9P983eeLokd5Ibgk5Fz8xH0cWyONkE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27337@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1023 bytes --]
New comment by Skirmisher on void-packages repository
https://github.com/void-linux/void-packages/issues/27337#issuecomment-749284979
Comment:
Seems pretty good all around. Standardizing the existing lib32/64 setup while pointing the multilib component to a separate prefix is a pragmatic approach that still leaves room for flexibility.
I do want to address the prefix location thing: cross toolchain prefixes are weird because they have libraries for the prefix arch in `usr/lib`, but have host arch binaries in `usr/bin`, making it inconsistent with a real install (especially since in a multiarch situation, you would be able to run the "native" versions of those tools anyway). I'm not sure if there's a way to work around the host-arch binaries, or if it would be straightforward to move the cross prefixes somewhere else, e.g. `/usr/cross/<prefix>`... If nothing else, though, I would find it reasonable to put multiarch prefixes in their own subdirectory like `/usr/multiarch` or `/usr/arch` or whatever else.
next prev parent reply other threads:[~2020-12-22 1:22 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-22 0:50 [ISSUE] tracking issue: " q66
2020-12-22 1:17 ` [RFC/tracking issue] " ahesford
2020-12-22 1:18 ` q66
2020-12-22 1:22 ` Skirmisher [this message]
2020-12-22 1:58 ` q66
2020-12-22 2:00 ` q66
2020-12-22 2:05 ` ericonr
2020-12-22 4:31 ` ericonr
2020-12-22 4:31 ` ericonr
2020-12-22 5:11 ` ericonr
2020-12-22 5:26 ` ericonr
2020-12-22 20:59 ` q66
2020-12-22 20:59 ` q66
2020-12-22 20:59 ` q66
2020-12-22 20:59 ` q66
2020-12-22 20:59 ` q66
2020-12-22 20:59 ` q66
2020-12-22 21:22 ` q66
2020-12-22 21:34 ` q66
2020-12-22 21:58 ` q66
2020-12-22 22:16 ` q66
2020-12-23 0:26 ` q66
2020-12-23 0:26 ` q66
2020-12-23 0:27 ` q66
2020-12-23 0:39 ` q66
2020-12-27 20:07 ` ericonr
2020-12-27 20:26 ` ericonr
2020-12-28 1:35 ` ericonr
2021-01-07 20:31 ` ahesford
2022-05-01 2:14 ` github-actions
2022-05-01 5:45 ` the-maldridge
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=20201222012254.H9F97Y3YIqxZu9P983eeLokd5Ibgk5Fz8xH0cWyONkE@z \
--to=skirmisher@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).