| 1 |
-----BEGIN PGP SIGNED MESSAGE-----
|
| 2 |
Hash: SHA1
|
| 3 |
|
| 4 |
On Thu, 20 Sep 2012 10:14:32 -0400
|
| 5 |
Ian Stakenvicius <axs@g.o> wrote:
|
| 6 |
> And, for support to be official for ebuilds or eclasses to query IUSE |
| 7 |
> (or other globals) within phase functions, then the 'spec' (PMS) is |
| 8 |
> probably all that needs to be 'fixed'. Right? |
| 9 |
|
| 10 |
First someone would have to check very very carefully that it's now
|
| 11 |
supported everywhere, including when using binaries, when doing VDB
|
| 12 |
loading, etc. We'd also have to make sure we're not going to be hit by
|
| 13 |
bash changing the behaviour of 'source' again...
|
| 14 |
|
| 15 |
> So, in EAPI=6, we propose something that'll make it official (ie a |
| 16 |
> querying function; or ensure that PMs can provide these variables |
| 17 |
> along with their proper 'effective' values, or their in-ebuild |
| 18 |
> 'explicit' values, or whatever it is we want to say can be relied |
| 19 |
> upon, to the environment). |
| 20 |
|
| 21 |
You'll have to be very very specific about where it will and won't
|
| 22 |
work. It definitely won't work everywhere in global scope, for example.
|
| 23 |
|
| 24 |
There's also the question of whether we effectively want to force
|
| 25 |
merging and normalising of variables to be done on the bash side, rather
|
| 26 |
than inside the package mangler.
|
| 27 |
|
| 28 |
- --
|
| 29 |
Ciaran McCreesh
|
| 30 |
-----BEGIN PGP SIGNATURE-----
|
| 31 |
Version: GnuPG v2.0.19 (GNU/Linux)
|
| 32 |
|
| 33 |
iEYEARECAAYFAlBbJ5IACgkQ96zL6DUtXhFA7wCcDnPCizqcqFImdkjSqcG599wU
|
| 34 |
PygAn2W/8qX9tjgQUYM1KXhcUeCnpCcK
|
| 35 |
=7kyg
|
| 36 |
-----END PGP SIGNATURE----- |
Archives