1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA256 |
3 |
|
4 |
On 20/09/12 10:26 AM, Ciaran McCreesh wrote: |
5 |
> On Thu, 20 Sep 2012 10:14:32 -0400 Ian Stakenvicius |
6 |
> <axs@g.o> wrote: |
7 |
>> And, for support to be official for ebuilds or eclasses to query |
8 |
>> IUSE (or other globals) within phase functions, then the 'spec' |
9 |
>> (PMS) is probably all that needs to be 'fixed'. Right? |
10 |
> |
11 |
> First someone would have to check very very carefully that it's |
12 |
> now supported everywhere, including when using binaries, when doing |
13 |
> VDB loading, etc. We'd also have to make sure we're not going to be |
14 |
> hit by bash changing the behaviour of 'source' again... |
15 |
> |
16 |
>> So, in EAPI=6, we propose something that'll make it official (ie |
17 |
>> a querying function; or ensure that PMs can provide these |
18 |
>> variables along with their proper 'effective' values, or their |
19 |
>> in-ebuild 'explicit' values, or whatever it is we want to say can |
20 |
>> be relied upon, to the environment). |
21 |
> |
22 |
> You'll have to be very very specific about where it will and won't |
23 |
> work. It definitely won't work everywhere in global scope, for |
24 |
> example. |
25 |
> |
26 |
> There's also the question of whether we effectively want to force |
27 |
> merging and normalising of variables to be done on the bash side, |
28 |
> rather than inside the package mangler. |
29 |
> |
30 |
|
31 |
*nod* |
32 |
|
33 |
I'm not tied to a particular implementation, rather just that the |
34 |
values of some of these global vars (IUSE, for instance) do seem to |
35 |
have a need to be available for querying during phase functions (and |
36 |
PMS will need to be updated to make this legal, via i assume a future |
37 |
EAPI) |
38 |
|
39 |
That said, since some vars are and must be made available from global |
40 |
scope (ie, "${S}"), I expect that it shouldn't be difficult to enforce |
41 |
effective ${IUSE} no matter what possible things bash might change. |
42 |
|
43 |
-----BEGIN PGP SIGNATURE----- |
44 |
Version: GnuPG v2.0.19 (GNU/Linux) |
45 |
|
46 |
iF4EAREIAAYFAlBbKswACgkQ2ugaI38ACPBAQAD/YwjnXJGgLTQ0Fhcv6XpHkCAc |
47 |
HokQhnN9i2Mu1aYikZcA/2bKlBCnVaPkjB7bQu1S+1BM8MAlmUi410IdYyYMldjn |
48 |
=Fp3a |
49 |
-----END PGP SIGNATURE----- |