Gentoo Archives: gentoo-dev

From: "Ulrich Müller" <ulm@g.o>
To: gentoo-dev@l.g.o
Cc: "Ulrich Müller" <ulm@g.o>, "Michał Górny" <mgorny@g.o>
Subject: [gentoo-dev] [PATCH 1/1] glep-0068: Allow EAPI 5 dependency specifications
Date: Wed, 22 Feb 2023 16:08:05
Message-Id: 20230222160704.6748-2-ulm@gentoo.org
In Reply to: [gentoo-dev] [PATCH 0/1] GLEP 68: Allow EAPI 5 dependency specifications by "Ulrich Müller"
1 This applies to the "restrict" attribute which is used with the
2 "maintainer", "longdescription", "flag", and "stabilize-allarches"
3 elements.
4
5 Closes: https://bugs.gentoo.org/895790
6 Reviewed-by: Michał Górny <mgorny@g.o>
7 Signed-off-by: Ulrich Müller <ulm@g.o>
8 ---
9 glep-0068.rst | 16 +++++++++++-----
10 1 file changed, 11 insertions(+), 5 deletions(-)
11
12 diff --git a/glep-0068.rst b/glep-0068.rst
13 index 9d10aaa..ca75991 100644
14 --- a/glep-0068.rst
15 +++ b/glep-0068.rst
16 @@ -4,9 +4,9 @@ Title: Package and category metadata
17 Author: Michał Górny <mgorny@g.o>
18 Type: Standards Track
19 Status: Final
20 -Version: 1.3
21 +Version: 1.4
22 Created: 2016-03-14
23 -Last-Modified: 2022-10-14
24 +Last-Modified: 2023-01-22
25 Post-History: 2016-03-16, 2018-02-20, 2022-05-22, 2022-10-07
26 Content-Type: text/x-rst
27 Requires: 67
28 @@ -118,7 +118,7 @@ of ``en`` is assumed.
29
30 Restriction specifiers are used whenever an element supports restricting to
31 specific package versions. In this case, each occurence of the element may
32 -contain an optional ``restrict=""`` attribute that contains an EAPI 0
33 +contain an optional ``restrict=""`` attribute that contains an EAPI 5
34 dependency specification that has to match one or more versions of the
35 package. In this case, the metadata provided by the element applies only to
36 the package versions matching the restriction.
37 @@ -341,8 +341,9 @@ added three clarifications to it:
38 - only package dependency specifications are allowed (i.e. no USE-conditionals
39 or multiple dependency specifications),
40
41 -- only EAPI=0 dependency specifications are allowed, since ``metadata.xml``
42 - provides no EAPI identification mechanism and it predates EAPI,
43 +- EAPI 5 dependency specifications are allowed. Although ``metadata.xml``
44 + provides no EAPI identification mechanism, the top-level profile directory
45 + specifies EAPI 5, and Portage supports EAPI 5 since 2012.
46
47 - only dependencies referencing the same package are allowed.
48
49 @@ -452,6 +453,11 @@ Example metadata.xml file
50 <email>developer@×××××××.com</email>
51 <name>Example Developer</name>
52 </maintainer>
53 + <maintainer type='person' restrict='dev-libs/foo:11'>
54 + <email>anotherdev@×××××××.com</email>
55 + <name>Another Developer</name>
56 + <description>CC only on bugs for libfoo.so.11</description>
57 + </maintainer>
58 <maintainer type='project'>
59 <email>project@×××××××.com</email>
60 <name>Example Project</name>
61 --
62 2.39.2