On 7/17/14, 2:28 PM, Pacho Ramos wrote: > 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?
+1 to moving KEYWORDS to ebuilds. Do we know what is the reason for doing this via enlightenment.eclass? Paweł
signature.asc
Description: OpenPGP digital signature
