[gentoo-dev] [PATCH] glep-0068: Add <stabilize-allarches/> element to metadata.xml

[gentoo-dev] [PATCH] glep-0068: Add <stabilize-allarches/> element to metadata.xml

[Michał Górny]

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

Re: [gentoo-dev] [PATCH] glep-0068: Add <stabilize-allarches/> element to metadata.xml

[Ulrich Mueller]

[-- Attachment #1: Type: text/plain, Size: 537 bytes --]

>>>>> On Tue, 20 Feb 2018, Michał Górny wrote:
 
> +- zero or more ``<stabilize-allarches/>`` elements, possibly restricted
> +  to specific package versions (at most one for each version) whose presence

Rather than versions, it might make more sense to allow restricting
this to specific slots. I suggest to update the "restrict" attribute
to EAPI 5 dependency specifications (either for this element only,
or globally).

> +  indicates that the appropriate ebuilds are suitable for ALLARCHES
> +  stabilization.

Ulrich

[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]

Re: [gentoo-dev] [PATCH] glep-0068: Add <stabilize-allarches/> element to metadata.xml

[Mart Raudsepp]

On Tue, 2018-02-20 at 22:58 +0100, Michał Górny wrote:
> @@ -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.
> +

ALLARCHES is a bugzilla keyword that happened to get referred to as
such for the action as well, in all its yelling glory.
I would prefer the action itself defined here, not refer to some
bugzilla keyword that lacks any reference citation and is known mainly
just from moderate maintainer experience or googling.

Re: [gentoo-dev] [PATCH] glep-0068: Add <stabilize-allarches/> element to metadata.xml

[Michał Górny]

W dniu śro, 21.02.2018 o godzinie 00∶32 +0100, użytkownik Ulrich Mueller
napisał:
> > > > > > On Tue, 20 Feb 2018, Michał Górny wrote:
> 
>  
> > +- zero or more ``<stabilize-allarches/>`` elements, possibly restricted
> > +  to specific package versions (at most one for each version) whose presence
> 
> Rather than versions, it might make more sense to allow restricting
> this to specific slots. I suggest to update the "restrict" attribute
> to EAPI 5 dependency specifications (either for this element only,
> or globally).
> 

Not sure if that's a good idea. Not that anything I know really parses
restrict="" but (unlike adding a new element) changing the semantics of
it is not backwards-compatible.

Also, should we allow USE-dependencies in it then? How should they be
evaluated?

-- 
Best regards,
Michał Górny

Re: [gentoo-dev] [PATCH] glep-0068: Add <stabilize-allarches/> element to metadata.xml

[Michał Górny]

W dniu śro, 21.02.2018 o godzinie 00∶32 +0100, użytkownik Ulrich Mueller
napisał:
> > > > > > On Tue, 20 Feb 2018, Michał Górny wrote:
> 
>  
> > +- zero or more ``<stabilize-allarches/>`` elements, possibly restricted
> > +  to specific package versions (at most one for each version) whose presence
> 
> Rather than versions, it might make more sense to allow restricting
> this to specific slots. I suggest to update the "restrict" attribute
> to EAPI 5 dependency specifications (either for this element only,
> or globally).
> 

One more thing: the current restrict="" can be evaluated purely
on ebuild name. Working with slots requires getting the complete
metadata.

-- 
Best regards,
Michał Górny

Re: [gentoo-dev] [PATCH] glep-0068: Add <stabilize-allarches/> element to metadata.xml

[Michał Górny]

W dniu śro, 21.02.2018 o godzinie 07∶56 +0200, użytkownik Mart Raudsepp
napisał:
> On Tue, 2018-02-20 at 22:58 +0100, Michał Górny wrote:
> > @@ -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.
> > +
> 
> ALLARCHES is a bugzilla keyword that happened to get referred to as
> such for the action as well, in all its yelling glory.
> I would prefer the action itself defined here, not refer to some
> bugzilla keyword that lacks any reference citation and is known mainly
> just from moderate maintainer experience or googling.
> 

v2 sent with more verbose explanation.

-- 
Best regards,
Michał Górny