| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
On 17/07/14 02:28 PM, Pacho Ramos wrote: |
| 5 |
> El jue, 17-07-2014 a las 17:03 +0100, Ciaran McCreesh escribió: |
| 6 |
>> On Thu, 17 Jul 2014 10:23:20 -0400 Rich Freeman |
| 7 |
>> <rich0@g.o> wrote: |
| 8 |
>>> I think that sticking KEYWORDS in an eclass is something that |
| 9 |
>>> should probably never happen. |
| 10 |
>> |
| 11 |
>> It used to be banned by PMS, for other reasons... |
| 12 |
>> |
| 13 |
> |
| 14 |
> I have just found this: |
| 15 |
> https://bugs.gentoo.org/show_bug.cgi?id=342185 |
| 16 |
> |
| 17 |
> Then, looks like they are refusing to change it :( |
| 18 |
> |
| 19 |
> |
| 20 |
|
| 21 |
|
| 22 |
OK, so, we're back to the complicated option -- a different set of |
| 23 |
KEYWORDS for each class of RELEASE (ie, RELEASE=true, RELEASE=false, |
| 24 |
or a new RELEASE=in-progress); ebuilds are set to in-progress for the |
| 25 |
particular set that are being stabilized, and KEYWORDS are adjusted in |
| 26 |
the eclass. |
| 27 |
|
| 28 |
I guess we'll have to wait until vapier's back to get it done, tho.. |
| 29 |
|
| 30 |
|
| 31 |
-----BEGIN PGP SIGNATURE----- |
| 32 |
Version: GnuPG v2.0.22 (GNU/Linux) |
| 33 |
|
| 34 |
iF4EAREIAAYFAlPIHFoACgkQ2ugaI38ACPD0eAD/QXb/bJuLVIb6zcKJhfDjqvbD |
| 35 |
x1ZUuMYGpO63oWMLs5QA+waGdHDawW5nGQ/MEqwzkwgJYbOz0pKgDDYlfll+mGJ8 |
| 36 |
=f6s7 |
| 37 |
-----END PGP SIGNATURE----- |
Archives