1 |
Pacho Ramos schrieb: |
2 |
> El jue, 17-07-2014 a las 23:14 +0200, Thomas Sachau escribió: |
3 |
>> Pacho Ramos schrieb: |
4 |
>>> I recently noticed this: |
5 |
>>> https://bugs.gentoo.org/show_bug.cgi?id=502836 |
6 |
>>> |
7 |
>>> imlib2 ebuild can only be stabilized in one round for all arches as |
8 |
>>> KEYWORDS are set in eclass depending on E_STATE="release". That has an |
9 |
>>> important drawback as forces all arches to be done at the same time and, |
10 |
>>> since some are much slower than others, forces all to wait for them. |
11 |
>>> And, as that can depend on even more stabilizations (like it's the case) |
12 |
>>> all that bugs blocking the stabilization need to also be done for *all* |
13 |
>>> arches before. |
14 |
>>> |
15 |
>>> I am not sure if any policy exists for this, but I would forbid to make |
16 |
>>> this due this issue. I would instead move to use KEYWORDS en ebuild as |
17 |
>>> done usually. |
18 |
>>> |
19 |
>>> What do you think? |
20 |
>>> |
21 |
>>> |
22 |
>>> |
23 |
>> |
24 |
>> You know that a KEYWORDS variable set in the ebuild after the inherit |
25 |
>> line does overwrite anything set by the eclass? |
26 |
>> So i dont really see, what the issue here actually should be. |
27 |
>> |
28 |
> |
29 |
> Should we start setting KEWORDS in imlib2 ebuild then? (for example for |
30 |
> https://bugs.gentoo.org/show_bug.cgi?id=502836 ) In that case, what is |
31 |
> the advantage for setting it in eclass too? |
32 |
> |
33 |
> |
34 |
> |
35 |
You obviously already did it, but yes, my suggestion is to set the |
36 |
KEYWORDS variable in the ebuild. |
37 |
|
38 |
The advantage for setting it in the eclass is in my eyes mostly for |
39 |
development in overlays (efl 1.7 libs and e17 have been in the overlay |
40 |
for a long time), since there are no arch teams to stabilize, so it is |
41 |
easier to set it based on the version then to manually adjust all |
42 |
keywords for each ebuild. |
43 |
|
44 |
-- |
45 |
|
46 |
Thomas Sachau |
47 |
Gentoo Linux Developer |