El 02/11/2012 18:32, Sander van der Burg - EWI
S.vanderBurgs.vanderb...@tudelft.nl
@ s.vanderb...@tudelft.nltudelft.nl s.vanderb...@tudelft.nl va
escriure:
Hello everyone,
Hi
Currently, I'm trying to deploy node.js on Mac OS X through the Nix
package manager. Unfortunately, it fails because
Hello!
A common problem for people trying to use Nix/Nixpkgs/Guix on non-NixOS
distros, especially Debian derivatives, is that their /bin/sh is not
Bash. On Debian and derivatives, it’s a symlink to /bin/dash.
When building without a chroot, things eventually fail because stdenv,
and sometimes
A common problem for people trying to use Nix/Nixpkgs/Guix on non-NixOS
distros, especially Debian derivatives, is that their /bin/sh is not
Bash. On Debian and derivatives, it’s a symlink to /bin/dash.
When building without a chroot, things eventually fail because stdenv,
and sometimes build
Hi Michael,
Michael Raskin 7c6f4...@mail.ru skribis:
I have some basic-chroot.nix, which is what basics I need to do Nix
builds and look at simple problems comfortably.
It is literally:
let nixpkgs = import nixpkgs {}; in with nixpkgs;
symlinkJoin chroot-system [
nixUnstable
Hi Michael,
Michael Raskin 7c6f4...@mail.ru skribis:
I have some basic-chroot.nix, which is what basics I need to do Nix
builds and look at simple problems comfortably.
It is literally:
let nixpkgs = import nixpkgs {}; in with nixpkgs;
symlinkJoin chroot-system [
nixUnstable
Hi,
Michael Raskin 7c6f4...@mail.ru skribis:
[...]
I was thinking that, instead of just bind-mounting /bin, we could have
at least a nix-daemon option that would allow the host code to specify
which file /bin/sh should point to. Even better would be to have an
additional ‘derivation’
So, I guess there would be a configuration option (marked as dangerous
and/or impure) to override what is taken from external environment for
a normal chroot build (ideally, nothing — maybe it is possible to use
even fake proc?).
What I had in mind was more an extension of DerivationInputs.
