On Wed, 07 Aug 2019 17:55:21 +0200 Ulrich Mueller <[email protected]> wrote:
> Plus, the eclasses explicitly allow KEYWORDS to be overridden by the
> ebuild:
>
> : ${KEYWORDS:=alpha amd64 arm arm64 hppa ia64 m68k ~mips ppc ppc64 ~riscv
> s390 sh sparc x86 ~ppc-aix ~x64-cygwin ~amd64-fbsd ~x86-fbsd ~amd64-linux
> ~x86-linux ~ppc-macos ~x64-macos ~x86-macos ~m68k-mint ~sparc-solaris
> ~sparc64-solaris ~x64-solaris ~x86-solaris}
I guess the clear limitation that the proposed policy would create, is
that it would be illegal for a package on say, riscv, to be stabilized,
if it depended on any acct-* packages.
Because the eclass would say "riscv ain't stable", and policy would say
"you can't change keywords on acct-*", which would necessitate that all
acct-* be marked stable for riscv via changing the eclass, in order for
the riscv package to be marked stable.
( Yes, this is not a risk now, but it would be an annoying situation
for anyone trying to promote riscv into being a stable arch )
pgp41wRXU3STR.pgp
Description: OpenPGP digital signature
