1 |
On Tue, 21 Dec 2010 15:46:25 +0100 |
2 |
Ulrich Mueller <ulm@g.o> wrote: |
3 |
> In file eapi-differences.tex, section "EAPI 4", PMS says: |
4 |
> ,---- |
5 |
> | EAPI 4 is EAPI 3 with the following changes: |
6 |
> | * PROPERTIES support is mandatory. |
7 |
> `---- |
8 |
> |
9 |
> Whereas in file dependencies.tex, subsection "Properties", it seems to |
10 |
> contradict the above: |
11 |
> ,---- |
12 |
> | The following tokens are permitted inside PROPERTIES: |
13 |
> | * interactive |
14 |
> | The package may require interaction with the user via the tty. |
15 |
> | |
16 |
> | Ebuilds may not rely upon any token being supported. |
17 |
> `---- |
18 |
> |
19 |
> Should the last sentence be deleted? |
20 |
|
21 |
No. PROPERTIES is purely advisory. The package manager may use it to |
22 |
handle builds differently, but ebuilds must not rely upon it. |
23 |
|
24 |
The "PROPERTIES support is mandatory" part refers to support for the |
25 |
metadata key itself. Since it was added in as a non-EAPI change, you |
26 |
couldn't rely upon metadata cache containing a value for it. |
27 |
|
28 |
-- |
29 |
Ciaran McCreesh |