Ferris McCormick wrote:
> 
> Um, not really --- this is too broad.  Some packages are not keyworded
> because no one has ever tried them.  We occasionally get keyword
> requests of the form "Please add ~sparc keyword to .... because I've
> been using it and it works fine" in response to which we do add the
> keyword if it does work.  No maintainer action involved, because the
> maintainer apparently doesn't know if the package works on sparc or not
> anyway.  A STABLEREQ is a different matter, masked packages are a
> different matter, but not just keywording.
> 

If the package were already keyworded ~arch on a few other archs I
wouldn't hesitate to add ~amd64 if it worked on amd64.  However, if a
package were ~arch on several archs I would not keyword it stable amd64
without the maintainer's input (or at least lack of response in the case
of an inactive maintainer).  I don't think maintainers need to be bugged
all the time, but they should be asked about making an ebuild stable for
the first time, or unmasking/etc.
-- 
[email protected] mailing list

Reply via email to