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