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