From: Alexis Ballier <aballier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: mgorny@gentoo.org
Subject: Re: [gentoo-dev] Getting proper USE_EXPAND variable(s) for multilib
Date: Mon, 21 Jan 2013 10:27:30 -0300 [thread overview]
Message-ID: <20130121102730.6ca8b6e4@gentoo.org> (raw)
In-Reply-To: <20130120201131.5afcbf48@pomiocik.lan>
On Sun, 20 Jan 2013 20:11:31 +0100
Michał Górny <mgorny@gentoo.org> wrote:
> Hello,
>
> There is a fair interest in multilib and while still early, it would
> be a good moment to decide on how USE flags to use for it.
>
> The current attempts are mostly using USE=multilib which is not really
> expressive and poor. What I would go for is a clear variable
> specifying which targets package is built for.
>
>
> This raises the following questions:
>
> 1) do we want the default ABI to be switchable?
I'd say no but I do not see any real problem with it.
> 2) do we want irrelevant ABIs to be visible to emerge users?
>
> By 2) I mean: do we want the users to see stuff like:
>
> MULTILIB_ABIS="amd64_abi1 amd64_abi2 -amd64_abi3 (-ppc64_abi1)
> (-ppc64_abi2) (-ppc64_abi3) ..."
>
> or just the relevant part.
just the relevant part, you'd probably need PM support here but showing
it all doesn't hurt, it's just less convenient.
>
> To be honest, I don't know if there's other way to hide USE flags than
> using USE_EXPAND_HIDDEN. If we want to use that, we'd have to split
> the flags per-arch, i.e. have:
>
> MULTILIB_AMD64="abi1 abi2 abi3"
> MULTILIB_PPC64="abi1 abi2 abi3"
>
> with appropriate USE_EXPAND_HIDDEN set by profiles.
I don't like that at all.
I'd go for ABI= the union of all the MULTILIB_ABIS variables (if there
is no name collision)
we certainly want skype to depend on libitneeds[abi_x86], not 'amd64?
( libitneeds[abi_amd64_x86] ) x86? ( libitneeds )'
Alexis.
next prev parent reply other threads:[~2013-01-21 13:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-20 19:11 [gentoo-dev] Getting proper USE_EXPAND variable(s) for multilib Michał Górny
2013-01-20 22:05 ` Sergei Trofimovich
2013-01-20 22:33 ` Michał Górny
2013-01-21 13:34 ` Alexis Ballier
2013-01-20 23:05 ` Thomas Sachau
2013-01-20 23:01 ` Thomas Sachau
2013-01-20 23:08 ` Michał Górny
2013-01-20 23:10 ` Gilles Dartiguelongue
2013-01-20 23:52 ` Thomas Sachau
2013-01-20 23:59 ` Chí-Thanh Christopher Nguyễn
2013-01-21 1:31 ` Matt Turner
2013-01-21 13:27 ` Alexis Ballier [this message]
2013-01-21 16:55 ` Michał Górny
2013-01-23 8:24 ` Michał Górny
2013-01-23 11:03 ` Alexis Ballier
2013-01-23 15:27 ` Michał Górny
2013-01-23 15:44 ` Michał Górny
2013-01-23 17:36 ` Alexey Shvetsov
2013-01-23 18:48 ` Alexis Ballier
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=20130121102730.6ca8b6e4@gentoo.org \
--to=aballier@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=mgorny@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