The Ruby gems problem is similar - and I agree with your assessment of wrappers providing paths.
I am thinking - eventually - a solution would be to embed the installation of an add-on into a proper nix-build. Each add-on would just become its own package. With Ruby gems that is feasible, I think. 'nix-gem install add-on.gem' would need to put the build and installation within nix-build. That way Nix is aware and can manage the environment. Only thing, as we don't know a gem beforehand, would it be possible to generate a nix expression on the fly? Or is that inadvisable? Pj. _______________________________________________ nix-dev mailing list [email protected] https://mail.cs.uu.nl/mailman/listinfo/nix-dev
