[patch] glep-0068: Allow EAPI 5 dependency specifications

0001-glep-0068-Allow-EAPI-5-dependency-specifications.patch (text/plain), 2.65 KB, created by Ulrich Müller on 2023-02-22 07:35:00 UTC

From acbe7c88500e50338e3efaf5811379dda4f36462 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Ulrich=20M=C3=BCller?= <[e-mail]>
Date: Wed, 22 Feb 2023 08:23:19 +0100
Subject: [PATCH] glep-0068: Allow EAPI 5 dependency specifications
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

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

Signed-off-by: Ulrich Müller <[e-mail]>
---
 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 <[e-mail]>
 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>[e-mail]</email>
         <name>Example Developer</name>
       </maintainer>
+      <maintainer type='person' restrict='dev-libs/foo:11'>
+        <email>[e-mail]</email>
+        <name>Another Developer</name>
+        <description>CC only on bugs for libfoo.so.11</description>
+      </maintainer>
       <maintainer type='project'>
         <email>[e-mail]</email>
         <name>Example Project</name>
-- 
2.39.2