From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 6C16D13861E for ; Wed, 23 Jan 2013 11:04:12 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 8FDE921C048; Wed, 23 Jan 2013 11:04:04 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 95CFEE0517 for ; Wed, 23 Jan 2013 11:04:03 +0000 (UTC) Received: from localhost (pc-234-79-101-190.cm.vtr.net [190.101.79.234]) (using SSLv3 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: aballier) by smtp.gentoo.org (Postfix) with ESMTPSA id 099E433DB44; Wed, 23 Jan 2013 11:04:01 +0000 (UTC) Date: Wed, 23 Jan 2013 08:03:56 -0300 From: Alexis Ballier To: gentoo-dev@lists.gentoo.org Cc: mgorny@gentoo.org Subject: Re: [gentoo-dev] Getting proper USE_EXPAND variable(s) for multilib Message-ID: <20130123080356.11ee5f6a@gentoo.org> In-Reply-To: <20130123092426.56745d6b@pomiocik.lan> References: <20130120201131.5afcbf48@pomiocik.lan> <20130121102730.6ca8b6e4@gentoo.org> <20130123092426.56745d6b@pomiocik.lan> Organization: Gentoo X-Mailer: Claws Mail 3.9.0 (GTK+ 2.24.14; x86_64-pc-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: b2995717-dddf-4e8d-b992-083fc1f7c774 X-Archives-Hash: b05ce81de3a63ae0f5eea03a2ced7d44 On Wed, 23 Jan 2013 09:24:26 +0100 Micha=C5=82 G=C3=B3rny wrote: > On Mon, 21 Jan 2013 10:27:30 -0300 > Alexis Ballier wrote: >=20 > > > 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: > > >=20 > > > MULTILIB_AMD64=3D"abi1 abi2 abi3" > > > MULTILIB_PPC64=3D"abi1 abi2 abi3" > > >=20 > > > with appropriate USE_EXPAND_HIDDEN set by profiles. > >=20 > > I don't like that at all. > > I'd go for ABI=3D 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 )' >=20 > Just a quick idea. >=20 > How would you feel about abi_x86_32? (similarly _64, _x32) >=20 > That would be almost natural names with the trick variable being > ABI_X86, therefore having all the fore-mentioned advantages. >=20 > The deps would look like: >=20 > libitneeds[abi_x86_32] >=20 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 :) Alexis.