1 |
>>>>> On Tue, 7 Jun 2011, Donnie Berkholz wrote: |
2 |
|
3 |
>> But it is not compliant with PMS: |
4 |
>> "If S is assigned in the global scope of an ebuild, then the |
5 |
>> restrictions of section 12.2 for global variables apply." (section 12.1) |
6 |
>> "Global variables must only contain invariant values." (section 12.2) |
7 |
|
8 |
> It seems compliant to me, as S is assigned an invariant value that |
9 |
> happens to contain the character '*', which is overwritten with a new |
10 |
> value as a local variable in ebuild functions. Sample code in listing |
11 |
> 12.1 in my copy of the PMS seems to suggest this is perfectly fine |
12 |
> behavior as long as the global invariant is restored after each |
13 |
> function. |
14 |
|
15 |
Even if it fulfills the restrictions for global variables, it is still |
16 |
an abuse of the spec, because PMS defines S as follows: |
17 |
"The full path to the temporary build directory, used by src_compile, |
18 |
src_install etc." |
19 |
|
20 |
And for EAPI 4 it will fail, because S is required to exist as initial |
21 |
working directory in most src_* phase functions. |
22 |
|
23 |
Ulrich |