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 1Kh7mA-0004BM-UB for garchives@archives.gentoo.org; Sat, 20 Sep 2008 19:05:51 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 9A169E053D; Sat, 20 Sep 2008 19:05:49 +0000 (UTC) Received: from smtp-3.tky.hut.fi (smtp03.tky.fi [82.130.63.73]) by pigeon.gentoo.org (Postfix) with SMTP id 4EB9AE053D for ; Sat, 20 Sep 2008 19:05:49 +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 M2008092022054527118 for ; Sat, 20 Sep 2008 22:05:45 +0300 Message-ID: <48D54987.6070200@gentoo.org> Date: Sat, 20 Sep 2008 22:05:43 +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> <20080920191527.3e1677bf@gentoo.org> In-Reply-To: <20080920191527.3e1677bf@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="------------enig7BB8AB69AA3A53C3C8C3F8A5" X-Archives-Salt: b28a3324-92cc-453c-8ccb-d5d01405d044 X-Archives-Hash: f08359dbb437c7e9aabe7562dd56df77 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig7BB8AB69AA3A53C3C8C3F8A5 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable Alexis Ballier kirjoitti: > Hi, >=20 >> When EAPI 2 goes live built_with_use should probably die for most >> cases.=20 >=20 > I don't understand here: you mean die like being removed or die like > the die call in an ebuild? If I understood correctly the following it > should be the latter. >=20 Well we could go with either but if there are valid use cases we need to = go with the latter. >> Are there valid use cases for built_with_use that are not >> covered by the use deps in EAPI 2? >=20 > I can think of checks like: > - foo is a dep/rdep of bar > - foo has a "plugin like" architecture > - bar will "work" with minimal foo > - most people will expect some features in bar that come with foo's > plugins > - we might want to display warnings for the most useful features > - having useflags in bar for each of foo's useflags doesn't seem wise >=20 >=20 > Ok that's not really a nice example but I can't think of anything > better at the moment. >=20 > By the way, how will the --missing option of built_with_use be handled > by eapi 2? >=20 > Alexis. Why should it be any different than what it is now? Regards, Petteri --------------enig7BB8AB69AA3A53C3C8C3F8A5 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 iEYEARECAAYFAkjVSYsACgkQcxLzpIGCsLS2dwCfQ94/DgwwqAc/I6BJ6kHEK8uQ oUkAn2iHfRmm0UPxPtdMkBTkfJGwBGVe =xUYm -----END PGP SIGNATURE----- --------------enig7BB8AB69AA3A53C3C8C3F8A5--