1 |
>>>>> On Wed, 08 Jun 2011, Hans de Graaff wrote: |
2 |
|
3 |
>> Even if it fulfills the restrictions for global variables, it is |
4 |
>> still an abuse of the spec, because PMS defines S as follows: |
5 |
>> "The full path to the temporary build directory, used by |
6 |
>> src_compile, src_install etc." |
7 |
|
8 |
> I don't see how setting S violates this specification. For each ruby |
9 |
> implementation that we build for the definition of S holds. It just |
10 |
> has a different value for each implementation. |
11 |
|
12 |
The value of S that is assigned in global scope (i.e. the one |
13 |
containing the wildcard) violates it. |
14 |
|
15 |
Ulrich |