[Nix-dev] Question about organising dependencies not in core nixpkgs?

[Thomas Hunger]

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 <lethalman88 at 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 at lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.science.uu.nl/pipermail/nix-dev/attachments/20150318/6c5871e1/attachment.html