1 |
Ferris McCormick wrote: |
2 |
> |
3 |
> Um, not really --- this is too broad. Some packages are not keyworded |
4 |
> because no one has ever tried them. We occasionally get keyword |
5 |
> requests of the form "Please add ~sparc keyword to .... because I've |
6 |
> been using it and it works fine" in response to which we do add the |
7 |
> keyword if it does work. No maintainer action involved, because the |
8 |
> maintainer apparently doesn't know if the package works on sparc or not |
9 |
> anyway. A STABLEREQ is a different matter, masked packages are a |
10 |
> different matter, but not just keywording. |
11 |
> |
12 |
|
13 |
If the package were already keyworded ~arch on a few other archs I |
14 |
wouldn't hesitate to add ~amd64 if it worked on amd64. However, if a |
15 |
package were ~arch on several archs I would not keyword it stable amd64 |
16 |
without the maintainer's input (or at least lack of response in the case |
17 |
of an inactive maintainer). I don't think maintainers need to be bugged |
18 |
all the time, but they should be asked about making an ebuild stable for |
19 |
the first time, or unmasking/etc. |
20 |
-- |
21 |
gentoo-dev@l.g.o mailing list |