[gentoo-pms] PROPERTIES contradiction?

[gentoo-pms] PROPERTIES contradiction?

[Ulrich Mueller]

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?

Ulrich

Re: [gentoo-pms] PROPERTIES contradiction?

[Christian Faulhammer]

[-- Attachment #1: Type: text/plain, Size: 767 bytes --]

Hi,

Ulrich Mueller <ulm@gentoo.org>:
> 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?

 I would say so.

-- 
Christian Faulhammer, Gentoo Lisp project
<URL:http://www.gentoo.org/proj/en/lisp/>, #gentoo-lisp on FreeNode

<URL:http://gentoo.faulhammer.org/>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-pms] PROPERTIES contradiction?

[Ciaran McCreesh]

[-- Attachment #1: Type: text/plain, Size: 987 bytes --]

On Tue, 21 Dec 2010 15:46:25 +0100
Ulrich Mueller <ulm@gentoo.org> 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

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]