[Nix-dev] Re: [PATCH 1/2] t/scons

[Peter Simons]

Hi 7c6f434c at mail.ru,

 > There are many places in nixpkgs, though, that rely on complex
 > time-consuming workarounds.

I'm not sure what you are referring to. What places do you have in mind?


 > And if the only relatively simple way to use scons is building a
 > custom scons binary each time - this is what will happen.

Well, I agree with the logic of your statement. It's just that the
premises doesn't hold: it is not true that building a custom SCons
binary is the only simple way to use it. Nix *does* use SCons to build
packages, and *none* of those builds requires a custom binary.


 > The original patch was created because current scons behaviour is
 > simply inconvenient for packaging scons-dependent software.

I'm not sure what you mean. What problems did you have packaging
SCons-dependent software?


 > It looks like the solution is replaced with ability to make custom
 > scons [...].

Actually, the opposite is true. Marc's solution was based on creating a
custom SCons binary, and that struck me as (and others) as overkill.
Instead, the build problems in the "v8" expression have now been
remedied by adding "importenv=PATH" to the SCons command line. That
solution is far less intrusive, and it does *not* require a custom SCons
binary.

Take care,
Peter