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