Quote from /usr/port/skel.ebuild:
# The ~ in front of the architecture indicates that the package is new and
# should be considered unstable until testing proves its stability. Once
# packages go stable the ~ prefix is removed. So, if you've confirmed that
# your ebuild works on x86 and ppc, you'd specify: KEYWORDS="~x86 ~ppc"
I would *think* that it should be 'KEYWORDS="x86 ppc"' instead?
Steps to Reproduce:
no ... the comment is explaining what the ~ means and then offhandedly
mentions how it move into stable
since you're making a new ebuild, the KEYWORDS should always start
(In reply to comment #1)
> no ... the comment is explaining what the ~ means and then offhandedly
> mentions how it move into stable
Arh, I get that now, but I just found it ambiguous. What about swapping the last
two sentences then? First explaining what ~ means, and what the KEYWORDS should
be, before finally mentioning when to remove ~ ?
A suggestion anyways.
> since you're making a new ebuild, the KEYWORDS should always start
> in unstable
I understood that much ;-)
tweaked as suggested, thanks