Note: Due to technical difficulties, the Archives are currently not up to date.
GMANE provides an alternative service for most mailing lists. c.f. bug 424647
On Tue, 21 Dec 2010 15:46:25 +0100
Ulrich Mueller <ulm@g.o> wrote:
> In file eapi-differences.tex, section "EAPI 4", PMS says:
> ,----
> | EAPI 4 is EAPI 3 with the following changes:
> | * PROPERTIES support is mandatory.
> `----
>
> Whereas in file dependencies.tex, subsection "Properties", it seems to
> contradict the above:
> ,----
> | The following tokens are permitted inside PROPERTIES:
> | * interactive
> | The package may require interaction with the user via the tty.
> |
> | Ebuilds may not rely upon any token being supported.
> `----
>
> Should the last sentence be deleted?
No. PROPERTIES is purely advisory. The package manager may use it to
handle builds differently, but ebuilds must not rely upon it.
The "PROPERTIES support is mandatory" part refers to support for the
metadata key itself. Since it was added in as a non-EAPI change, you
couldn't rely upon metadata cache containing a value for it.
--
Ciaran McCreesh
|
|
