[gentoo-commits] data/glep:glep39 commit in: /

["Ulrich Müller" <ulm@gentoo.org>]

commit:     d9ee35e0bd53b28e7cc1ffd6f2c4e4f1ad028b0a
Author:     Ulrich Müller <ulm <AT> gentoo <DOT> org>
AuthorDate: Wed Feb 22 07:23:19 2023 +0000
Commit:     Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Wed Feb 22 15:59:52 2023 +0000
URL:        https://gitweb.gentoo.org/data/glep.git/commit/?id=d9ee35e0

glep-0068: Allow EAPI 5 dependency specifications

This applies to the "restrict" attribute which is used with the
"maintainer", "longdescription", "flag", and "stabilize-allarches"
elements.

Closes: https://bugs.gentoo.org/895790
Reviewed-by: Michał Górny <mgorny <AT> gentoo.org>
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>

 glep-0068.rst | 16 +++++++++++-----
 1 file changed, 11 insertions(+), 5 deletions(-)

diff --git a/glep-0068.rst b/glep-0068.rst
index 9d10aaa..ca75991 100644
--- a/glep-0068.rst
+++ b/glep-0068.rst
@@ -4,9 +4,9 @@ Title: Package and category metadata
 Author: Michał Górny <mgorny@gentoo.org>
 Type: Standards Track
 Status: Final
-Version: 1.3
+Version: 1.4
 Created: 2016-03-14
-Last-Modified: 2022-10-14
+Last-Modified: 2023-01-22
 Post-History: 2016-03-16, 2018-02-20, 2022-05-22, 2022-10-07
 Content-Type: text/x-rst
 Requires: 67
@@ -118,7 +118,7 @@ of ``en`` is assumed.
 
 Restriction specifiers are used whenever an element supports restricting to
 specific package versions. In this case, each occurence of the element may
-contain an optional ``restrict=""`` attribute that contains an EAPI 0
+contain an optional ``restrict=""`` attribute that contains an EAPI 5
 dependency specification that has to match one or more versions of the
 package. In this case, the metadata provided by the element applies only to
 the package versions matching the restriction.
@@ -341,8 +341,9 @@ added three clarifications to it:
 - only package dependency specifications are allowed (i.e. no USE-conditionals
   or multiple dependency specifications),
 
-- only EAPI=0 dependency specifications are allowed, since ``metadata.xml``
-  provides no EAPI identification mechanism and it predates EAPI,
+- EAPI 5 dependency specifications are allowed. Although ``metadata.xml``
+  provides no EAPI identification mechanism, the top-level profile directory
+  specifies EAPI 5, and Portage supports EAPI 5 since 2012.
 
 - only dependencies referencing the same package are allowed.
 
@@ -452,6 +453,11 @@ Example metadata.xml file
         <email>developer@example.com</email>
         <name>Example Developer</name>
       </maintainer>
+      <maintainer type='person' restrict='dev-libs/foo:11'>
+        <email>anotherdev@example.com</email>
+        <name>Another Developer</name>
+        <description>CC only on bugs for libfoo.so.11</description>
+      </maintainer>
       <maintainer type='project'>
         <email>project@example.com</email>
         <name>Example Project</name>