1 |
El jue, 17-07-2014 a las 23:14 +0200, Thomas Sachau escribió: |
2 |
> Pacho Ramos schrieb: |
3 |
> > I recently noticed this: |
4 |
> > https://bugs.gentoo.org/show_bug.cgi?id=502836 |
5 |
> > |
6 |
> > imlib2 ebuild can only be stabilized in one round for all arches as |
7 |
> > KEYWORDS are set in eclass depending on E_STATE="release". That has an |
8 |
> > important drawback as forces all arches to be done at the same time and, |
9 |
> > since some are much slower than others, forces all to wait for them. |
10 |
> > And, as that can depend on even more stabilizations (like it's the case) |
11 |
> > all that bugs blocking the stabilization need to also be done for *all* |
12 |
> > arches before. |
13 |
> > |
14 |
> > I am not sure if any policy exists for this, but I would forbid to make |
15 |
> > this due this issue. I would instead move to use KEYWORDS en ebuild as |
16 |
> > done usually. |
17 |
> > |
18 |
> > What do you think? |
19 |
> > |
20 |
> > |
21 |
> > |
22 |
> |
23 |
> You know that a KEYWORDS variable set in the ebuild after the inherit |
24 |
> line does overwrite anything set by the eclass? |
25 |
> So i dont really see, what the issue here actually should be. |
26 |
> |
27 |
|
28 |
Should we start setting KEWORDS in imlib2 ebuild then? (for example for |
29 |
https://bugs.gentoo.org/show_bug.cgi?id=502836 ) In that case, what is |
30 |
the advantage for setting it in eclass too? |