Eelco Dolstra wrote: > The problem is that you are running nix-build inside the Nix store ... > The real problem however is that you shouldn't edit the Nix expressions in > the channel, which are strictly read-only... > So developers should do a checkout of the Nixpkgs tree:
> $ svn co https://svn.cs.uu.nl:12443/repos/trace/nixpkgs/trunk nixpkgs > and hack on that. (Or you can grab a Nixpkgs tarball, but a SVN checkout will > make it much easier to contribute changes :-) Thanks, building those additional apps works now. I checked out Nixpkgs from SVN and made that the default: nix-env -I /root/nix/nixpkgs/pkgs/top-level/all-packages.nix I suppose, that channels cannot be used while doing things this way? I was surprised, that mc (midnight commander) which built successfully in NixOS suddenly had an additional dependency on X11 when trying to buid in Nix on Debian. I thought, that it is impossible to have undeclared dependencies in Nix? Here is the expression which built successfully on NixOS-0.1pre8658: {stdenv, fetchurl, pkgconfig, glib, ncurses, libX11}: stdenv.mkDerivation { name = "mc-4.6.1"; src = fetchurl { url = http://www.ibiblio.org/pub/Linux/utils/file/managers/mc/mc-4.6.1.tar.gz; md5 = "18b20db6e40480a53bac2870c56fc3c4"; }; buildInputs = [pkgconfig glib ncurses]; configureFlags = "--with-screen=ncurses"; } When building with Nix on Debian Etch I had to add X11 as an additional dependency: buildInputs = [pkgconfig glib ncurses libX11]; How is this possible? ____________________________________________________________________________________ TV dinner still cooling? Check out "Tonight's Picks" on Yahoo! TV. http://tv.yahoo.com/ _______________________________________________ nix-dev mailing list [email protected] https://mail.cs.uu.nl/mailman/listinfo/nix-dev
