Thanks. That would require having the shell.nix library locally already AFAICT. To rephrase slightly. Ideally I'd like to be able to do:
myLibrary = fetchurl { ... }; extraDepends = import "${myLibrary}/depends.nix"; buildDepends = [ ... ] ++ extraDepends; Does that make sense? ~ On 18 March 2015 at 10:31, Luca Bruno <lethalma...@gmail.com> wrote: > On 18/03/2015 11:26, Thomas Hunger wrote: > > Hi, > > > > I usually include a shell.nix file in my libraries for development. If > > I have a dependency not in core nixpkgs then I add a local > > mkDerivation using "let pkg = ... in {}" to shell.nix (e.g. [1]). > > > > If I now want to use my library in another context, say nixops, I have > > to duplicate the shell.nix content because I cannot import from a > > project I'm depending on. > > > > I considered having a separate repository of nix expressions that is > > used for shell.nix as well as nixops but that makes it hard to release > > a standalone libraries on github. > Then make nixops import stuff from your shell.nix ? > _______________________________________________ > nix-dev mailing list > nix-dev@lists.science.uu.nl > http://lists.science.uu.nl/mailman/listinfo/nix-dev >
_______________________________________________ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev