From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1KiEzd-0001SV-Cu for garchives@archives.gentoo.org; Tue, 23 Sep 2008 21:00:21 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 639A8E0420; Tue, 23 Sep 2008 21:00:20 +0000 (UTC) Received: from smtp-3.tky.hut.fi (smtp03.tky.fi [82.130.63.73]) by pigeon.gentoo.org (Postfix) with SMTP id 16F4FE0420 for ; Tue, 23 Sep 2008 21:00:19 +0000 (UTC) Received: from [82.130.46.209] ([82.130.46.209]) by smtp-3.tky.hut.fi (SMSSMTP 4.1.9.35) with SMTP id M2008092400001823282 for ; Wed, 24 Sep 2008 00:00:18 +0300 Message-ID: <48D958E2.2060609@gentoo.org> Date: Wed, 24 Sep 2008 00:00:18 +0300 From: =?UTF-8?B?UGV0dGVyaSBSw6R0eQ==?= User-Agent: Thunderbird 2.0.0.16 (X11/20080729) 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 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Making built_with_use die by default with EAPI 2 References: <48D524ED.7080705@gentoo.org> <200809211335.53107.levertond@googlemail.com> <48D7FF30.1040709@gentoo.org> <200809231141.47863.bo.andresen@zlin.dk> <48D952A8.6050201@gentoo.org> <20080923224435.73f6e7af@gentoo.org> In-Reply-To: <20080923224435.73f6e7af@gentoo.org> X-Enigmail-Version: 0.95.6 OpenPGP: url=http://users.tkk.fi/~praty/public.asc Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig1D63894DF3DEEA9403AF4F84" X-Archives-Salt: 4cab296f-a8a8-4acd-b5da-f5e69a7e7ee6 X-Archives-Hash: 885ea482d94f612ede3c6b46ea4ef1de This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig1D63894DF3DEEA9403AF4F84 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable Alexis Ballier kirjoitti: > On Tue, 23 Sep 2008 23:33:44 +0300 > Petteri R=C3=A4ty wrote: >=20 >> Bo =C3=98rsted Andresen kirjoitti: >>> On Monday 22 September 2008 22:25:20 Petteri R=C3=A4ty wrote: >>>>> If you mean something like >>>>> >>>>> built_with_use cat/foo coolfeature || ewarn "bar will be more >>>>> useful if you rebuild cat/foo with USE=3Dcoolfeature"=20 >>>>> >>>>> then you can use >>>>> >>>>> has_version 'cat/foo[coolfeature]' || ... >>>>> >>>>> instead. >>>> What does this report if cat/foo does not have coolfeature use >>>> flag in some version? Meaning can this support cases which need >>>> --missing true. >>> False. If for instance coolfeature was made optional in >=3Dpv you >>> can use logic like: >>> >>> if has_version '>=3Dcat/foo-pv' && ! has_version >>> 'cat/foo[coolfeature]'; then ewarn '...' >>> fi >>> >> I think this should cover all the current functionality with=20 >> built_with_use.=20 >=20 > This is just an ugly hack. Think about a package that has coolfeature > useflag removed and enabled by default for a couple of releases because= > it wouldn't build without it and once upstream sorted out everything > the useflag is coming back. Missing useflags that are assumed to be > enabled have nothing to do with the package version being greater than > a given number. >=20 > I would *really* prefer having big warnings when using built_with_use > in EAPI 2; that way we can see how things are in practice and then > maybe make built_with_use die for a later eapi or once all the tree is > converted to eapi 2 remove it. >=20 > Alexis. Well we could replace the die with eerror but eventually we should get=20 rid of vdb access directly by ebuilds. Maybe the next EAPI should add=20 something similar to portageq as an abstraction layer. betelgeuse@pena /usr/portage/eclass $ portageq metadata / installed=20 $(portageq match / sys-devel/gcc:4.3) USE elibc_glibc gcj kernel_linux libffi openmp userland_GNU x86 Regards, Petteri --------------enig1D63894DF3DEEA9403AF4F84 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkjZWOUACgkQcxLzpIGCsLRyZgCfeITHp7RxQceKsKWad6REnnGL w6oAn21rQzoNYGGScRrwXtfXfdPGcBA4 =l6cE -----END PGP SIGNATURE----- --------------enig1D63894DF3DEEA9403AF4F84--