On Thu, 2019-10-10 at 16:49 +0200, Ulrich Mueller wrote: > Most packages in the app-emacs category have stabilize-allarches in > their metadata because they are arch independent. However, their > keywords don't reflect this and differ from package to package, mostly > for historical reasons. > > So, I would like to mass keyword all ebuilds in app-emacs (as far as > stabilize-allarches applies to them) to the intersection of keywords > of their dependencies. Same applies to stabilisation; if an ebuild is > stable on amd64, I would stabilise it on all other arches, as far as > dependencies allow it. > > Also, any new package added to app-emacs in future would start out with > the complete set of keywords. (I am aware that this doesn't agree with > the policy as it is documented in the devmanual: > https://devmanual.gentoo.org/keywording/index.html#keywording-new-packages) > > Any objections? >
Wasn't ALLARCHES supposed to be applied only if a previous version had a stable keyword on the arch in question? I.e. if it has been tested by arch team at least once? -- Best regards, Michał Górny
signature.asc
Description: This is a digitally signed message part
