From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: tommy@gentoo.org
Subject: Re: [gentoo-dev] Getting proper USE_EXPAND variable(s) for multilib
Date: Mon, 21 Jan 2013 00:08:48 +0100 [thread overview]
Message-ID: <20130121000848.78c7ea7e@pomiocik.lan> (raw)
In-Reply-To: <50FC7731.2090708@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1553 bytes --]
On Mon, 21 Jan 2013 00:01:05 +0100
Thomas Sachau <tommy@gentoo.org> wrote:
> Michał Górny schrieb:
> > 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?
> >
> > 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.
> >
> > 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.
> >
> >
> > What are your thoughts? Which arches would like to use multilib? What
> > names for ABIs do you suggest?
> >
>
> So you want to re-implement multilib-portage in an eclass without the
> additional benefits a package-manager level implementation has?
Could you stay on topic, please?
--
Best regards,
Michał Górny
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 316 bytes --]
next prev parent reply other threads:[~2013-01-20 23:08 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 [this message]
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
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=20130121000848.78c7ea7e@pomiocik.lan \
--to=mgorny@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=tommy@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