-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 17/07/14 02:28 PM, Pacho Ramos wrote: > El jue, 17-07-2014 a las 17:03 +0100, Ciaran McCreesh escribió: >> On Thu, 17 Jul 2014 10:23:20 -0400 Rich Freeman >> <ri...@gentoo.org> wrote: >>> I think that sticking KEYWORDS in an eclass is something that >>> should probably never happen. >> >> It used to be banned by PMS, for other reasons... >> > > I have just found this: > https://bugs.gentoo.org/show_bug.cgi?id=342185 > > Then, looks like they are refusing to change it :( > >
OK, so, we're back to the complicated option -- a different set of KEYWORDS for each class of RELEASE (ie, RELEASE=true, RELEASE=false, or a new RELEASE=in-progress); ebuilds are set to in-progress for the particular set that are being stabilized, and KEYWORDS are adjusted in the eclass. I guess we'll have to wait until vapier's back to get it done, tho.. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlPIHFoACgkQ2ugaI38ACPD0eAD/QXb/bJuLVIb6zcKJhfDjqvbD x1ZUuMYGpO63oWMLs5QA+waGdHDawW5nGQ/MEqwzkwgJYbOz0pKgDDYlfll+mGJ8 =f6s7 -----END PGP SIGNATURE-----
