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