Hi Marc, did you read my last posting? I would love to know what you think about the dependency handling approach I described in January [1]; here is the relevant snippet for your convenience:
>> libA requires libB. If you install libA into ~/.nix-profile/ it will >> be broken. > > I can think of the following possible solutions to this problem: > > (a) we don't care. The installation process might detect the missing > dependency and it might warn the user, but ultimately it's the > users decision how to remedy the situation. > > (b) Patch libA to extend "sys.path" as required before trying to import > libB. It's not pretty -- particularly if libA consists of a large > number of individual files --, but it does solve the problem and > requires no user action whatsoever. > > (c) Have libA create a file $out/etc/profile.d/libA.sh that sets > PYTHONPATH to include libB. This solution is rather non-intrusive > and lightweight, but it does require the user to source those > profiles to ensure that her environment is set up correctly. What do you think about those approaches? Take care, Peter [1] http://article.gmane.org/gmane.linux.distributions.nixos/1447 _______________________________________________ nix-dev mailing list nix-dev@cs.uu.nl https://mail.cs.uu.nl/mailman/listinfo/nix-dev
