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 D02671385A3 for ; Sun, 20 Jan 2013 19:11:05 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D19BE21C19C; Sun, 20 Jan 2013 19:10:58 +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 CC0F421C193 for ; Sun, 20 Jan 2013 19:10:57 +0000 (UTC) Received: from pomiocik.lan (213-238-105-25.adsl.inetia.pl [213.238.105.25]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: mgorny) by smtp.gentoo.org (Postfix) with ESMTPSA id 4D71D33DADC; Sun, 20 Jan 2013 19:10:56 +0000 (UTC) Date: Sun, 20 Jan 2013 20:11:31 +0100 From: =?UTF-8?B?TWljaGHFgiBHw7Nybnk=?= To: Gentoo Developer Mailing List Subject: [gentoo-dev] Getting proper USE_EXPAND variable(s) for multilib Message-ID: <20130120201131.5afcbf48@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: multipart/signed; micalg=PGP-SHA256; boundary="Sig_/_MaNiAlVBCe3ZA_5/YlxAaW"; protocol="application/pgp-signature" X-Archives-Salt: b6c9c40c-82cb-4da3-aa50-8368620ff266 X-Archives-Hash: 93c08663338d529b6ad7e42a90fd42a0 --Sig_/_MaNiAlVBCe3ZA_5/YlxAaW Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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=3Dmultilib 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=3D"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=3D"abi1 abi2 abi3" MULTILIB_PPC64=3D"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? --=20 Best regards, Micha=C5=82 G=C3=B3rny --Sig_/_MaNiAlVBCe3ZA_5/YlxAaW Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iJwEAQEIAAYFAlD8QWMACgkQfXuS5UK5QB1WxQQAiTLrQk0+D2Mhqd5D+LoS3inw D5bR8dfU3OkTYoA2rWoVGyLzksHpVlUXvw6afRwt8Duc0waVNh5Z4FDWaUKI96jT /UUd7W7ZzqCK+nL+4rGTGjzSSDFydl2/A2lBU2gfwhsjDD1rFovtQLlLulZCKeVp XfFcQxp/dMfTa3DZuxk= =kEnB -----END PGP SIGNATURE----- --Sig_/_MaNiAlVBCe3ZA_5/YlxAaW--