-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Santiago M. Mola wrote: > On Sat, Aug 2, 2008 at 12:26 PM, Zac Medico <[EMAIL PROTECTED]> wrote: >> Mike Auty wrote: >> >>> If there's need for a new class of ebuild information (such as a new >>> way of categorizing ebuilds by feature), perhaps we should add an ebuild >>> features variable specifically for the purpose? >> That requires an EAPI bump, which also means that it can't be used >> in ebuilds with EAPI 0 or 1. The RESTRICT solution is simpler and we >> can use it right now in any ebuild. >> > > I don't think we're in a hurry for this feature, so I don't see the > need of using suboptimal hacks in order to avoid an EAPI bump. > Furthermore, EAPI 2 is supposed to be done in the near future, right? > > Regards,
I don't view the RESTRICT=live idea as "suboptimal" or "a hack" in any way. I see it as a legitimate use of an existing ebuild variable that's already used for lots of other legitimate purposes. Zac -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkiU3toACgkQ/ejvha5XGaOqJQCgp0VTgcLgsyqvTMOl4yAEv+M9 Al8AoJlwWW3y3CIy4nlTfvY+QnouVFuQ =XMyh -----END PGP SIGNATURE-----
