public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: aballier@gentoo.org
Subject: Re: [gentoo-dev] Getting proper USE_EXPAND variable(s) for multilib
Date: Wed, 23 Jan 2013 16:27:17 +0100	[thread overview]
Message-ID: <20130123162717.204ce792@pomiocik.lan> (raw)
In-Reply-To: <20130123080356.11ee5f6a@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1748 bytes --]

On Wed, 23 Jan 2013 08:03:56 -0300
Alexis Ballier <aballier@gentoo.org> wrote:

> On Wed, 23 Jan 2013 09:24:26 +0100
> Michał Górny <mgorny@gentoo.org> wrote:
> 
> > On Mon, 21 Jan 2013 10:27:30 -0300
> > Alexis Ballier <aballier@gentoo.org> wrote:
> > 
> > > > 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 )'
> > 
> > Just a quick idea.
> > 
> > How would you feel about abi_x86_32? (similarly _64, _x32)
> > 
> > That would be almost natural names with the trick variable being
> > ABI_X86, therefore having all the fore-mentioned advantages.
> > 
> > The deps would look like:
> > 
> >   libitneeds[abi_x86_32]
> > 
> 
> Sounds good too, I just would want it to be shared between arches that
> can: amd64/x86/x32, ppc/ppc64, mips, sparc32/sparc64, etc.
> You mean you will hide ABI_X86 USE_EXPAND on non-x86 arches, right ?
> This would have all the benefits I think, very good idea :)

Yes.

I'm currently looking for a clean way to hide it without having to
repeat that in a dozen profiles. But it seems that portage and PMS
disagree again about the shape of USE_EXPAND_HIDDEN...

-- 
Best regards,
Michał Górny

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 316 bytes --]

  reply	other threads:[~2013-01-23 15:26 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
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 [this message]
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=20130123162717.204ce792@pomiocik.lan \
    --to=mgorny@gentoo.org \
    --cc=aballier@gentoo.org \
    --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