From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: "Michał Górny" <mgorny@gentoo.org>
Subject: [gentoo-dev] [PATCH] glep-0068: Add <stabilize-allarches/> element to metadata.xml
Date: Tue, 20 Feb 2018 22:58:37 +0100 [thread overview]
Message-ID: <20180220215837.18255-1-mgorny@gentoo.org> (raw)
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.
---
glep-0068.rst | 11 ++++++++---
1 file changed, 8 insertions(+), 3 deletions(-)
diff --git a/glep-0068.rst b/glep-0068.rst
index e8cba5d..f1f9ff5 100644
--- a/glep-0068.rst
+++ b/glep-0068.rst
@@ -4,10 +4,10 @@ Title: Package and category metadata
Author: Michał Górny <mgorny@gentoo.org>
Type: Standards Track
Status: Final
-Version: 1
+Version: 1.1
Created: 2016-03-14
-Last-Modified: 2017-05-05
-Post-History: 2016-03-16
+Last-Modified: 2018-02-20
+Post-History: 2018-02-20, 2016-03-16
Content-Type: text/x-rst
Requires: 67
Replaces: 34, 46, 56
@@ -147,6 +147,11 @@ element can contain, in any order:
languages (at most one for each language), as detailed
in `Slot descriptions`_.
+- zero or more ``<stabilize-allarches/>`` elements, possibly restricted
+ to specific package versions (at most one for each version) whose presence
+ indicates that the appropriate ebuilds are suitable for ALLARCHES
+ stabilization.
+
- zero or more ``<use/>`` elements containing USE flag descriptions
in different languages (at most one for each language), as detailed
in `USE flag descriptions`_.
--
2.16.2
next reply other threads:[~2018-02-20 21:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-20 21:58 Michał Górny [this message]
2018-02-20 23:32 ` [gentoo-dev] [PATCH] glep-0068: Add <stabilize-allarches/> element to metadata.xml Ulrich Mueller
2018-02-21 8:14 ` Michał Górny
2018-02-21 8:37 ` Michał Górny
2018-02-21 5:56 ` Mart Raudsepp
2018-02-21 8:37 ` Michał Górny
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180220215837.18255-1-mgorny@gentoo.org \
--to=mgorny@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox