Please approve the changes suggested in [1], that is adding '<stabilize-allarches/>' element to indicate that the package is suitable for ALLARCHES stabilization. The proposal got two comments: from leio suggesting improving description, and from ulm suggesting extending restrict='' syntax. The former was addressed in v2 while the latter I believe could be done as a separate change independent of this. [1]:https://archives.gentoo.org/gentoo-dev/message/ae4f89a9697f623df500b7d44d66c215
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/data/glep.git/commit/?id=6f4d97c0db20af6e3d75063b118f3756983a589a commit 6f4d97c0db20af6e3d75063b118f3756983a589a Author: Michał Górny <mgorny@gentoo.org> AuthorDate: 2018-02-20 21:51:08 +0000 Commit: Michał Górny <mgorny@gentoo.org> CommitDate: 2018-03-11 19:20:17 +0000 glep-0068: Add <stabilize-allarches/> element to metadata.xml Add a new <stabilize-allarches/> element to metadata.xml whose presence can be used to indicate that the package is suitable for ALLARCHES stabilization. Unlike the current system, this makes it possible to easily determine when packages can be stabilized wrt ALLARCHES independently of who requests the stabilization. For example, in Python ecosystem there are some packages which have C extensions or known-unportable code which we do not want to handle through ALLARCHES. Right now we have to either remember them or recheck for them when firing the stablereq, or — more commonly — we end up not using ALLARCHES when we could. Storing this information per-package will not only make it easier to determine whether ALLARCHES is applicable but also introduce some automation to determine that and react accordingly. Approved on 2018-03-11 Council meeting. Closes: https://bugs.gentoo.org/649740 glep-0068.rst | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-)
