| 1 |
On Wed, 07 Aug 2019 17:55:21 +0200 |
| 2 |
Ulrich Mueller <ulm@g.o> wrote: |
| 3 |
|
| 4 |
> Plus, the eclasses explicitly allow KEYWORDS to be overridden by the |
| 5 |
> ebuild: |
| 6 |
> |
| 7 |
> : ${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} |
| 8 |
|
| 9 |
I guess the clear limitation that the proposed policy would create, is |
| 10 |
that it would be illegal for a package on say, riscv, to be stabilized, |
| 11 |
if it depended on any acct-* packages. |
| 12 |
|
| 13 |
Because the eclass would say "riscv ain't stable", and policy would say |
| 14 |
"you can't change keywords on acct-*", which would necessitate that all |
| 15 |
acct-* be marked stable for riscv via changing the eclass, in order for |
| 16 |
the riscv package to be marked stable. |
| 17 |
|
| 18 |
( Yes, this is not a risk now, but it would be an annoying situation |
| 19 |
for anyone trying to promote riscv into being a stable arch ) |
Archives