1 |
On Tue, 2011-06-07 at 20:16 +0200, Ulrich Mueller wrote: |
2 |
|
3 |
> Even if it fulfills the restrictions for global variables, it is still |
4 |
> an abuse of the spec, because PMS defines S as follows: |
5 |
> "The full path to the temporary build directory, used by src_compile, |
6 |
> 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 has |
10 |
a different value for each implementation. |
11 |
|
12 |
> And for EAPI 4 it will fail, because S is required to exist as initial |
13 |
> working directory in most src_* phase functions. |
14 |
|
15 |
Correct, so in EAPI 4 we now set the RUBY_S variable to handle the |
16 |
initial setup, and then we set S as part of the environment setup when |
17 |
we are iterating through each ruby implementation within each of the PMS |
18 |
phases. |
19 |
|
20 |
Kind regards, |
21 |
|
22 |
Hans |