Am 07.07.2017 um 08:07 schrieb Vladimír Čunát via nix-dev:
> That's how it's commonly done in nixpkgs. If you want a *separate*
> expression that depends on nixpkgs, you may e.g. start by adding this
> line to the beginning of the file:
> with import <nixpkgs> {};
> instead of
> { stdenv, something1, something2, ... }:
Another solution (at least commonly used here at Flying Circus IO):
* leave the package expr as-is
* call it with the idiom
nix-build -E 'with import <nixpkgs> {}; callPackage ./hello.nix {}'
HTH
Christian
--
Dipl-Inf. Christian Kauhaus <>< · k...@flyingcircus.io · +49 345 219401-0
Flying Circus Internet Operations GmbH · http://flyingcircus.io
Forsterstraße 29 · 06112 Halle (Saale) · Deutschland
HR Stendal 21169 · Geschäftsführer: Christian Theune, Christian Zagrodnick
signature.asc
Description: OpenPGP digital signature
_______________________________________________ nix-dev mailing list nix-dev@lists.science.uu.nl https://mailman.science.uu.nl/mailman/listinfo/nix-dev
