<johnw>
if I have a buildEnv, how do I enter a nix-shell so that the *dependencies* of that build env are in scope?
<LnL>
well -p behaves differently
<johnw>
yeah, I need -p
<LnL>
either you use something like nix-shell -I nixpkgs=/path/to/nixpkgs -p foo
<johnw>
yeah, gross
<johnw>
I'll just go back to myEnvFun for now
<johnw>
nix-shell -I nixpkgs=$HOME/src/nix/darwin -p pkgs.ghc82Env does not work
<LnL>
ah right, it expects <nixpkgs> to be an actual nixpkgs repo :)
<johnw>
well, myEnvFun works really well, so I'd prefer if it just received some love, rather than being given all these messy and incomplete workarounds
<LnL>
I tried to implement the functionality using nix-shell a while back
<LnL>
it worked but nix would gc stuff even tho I had a reference to a drv
Sonarpulse has joined #nix-darwin
<johnw>
nix still gc's all of my tarballs
<johnw>
even though I have every option on to keep as much as possible
<johnw>
the only real solution is just to not gc
<dhess>
johnw: pong
<johnw>
dhess: I just posted on github, never mind ehre
<dhess>
johnw: do those overlapping attrs evaluate to the same derivation or will they conflict?
<johnw>
actually, I think the overlap was a problem in my build recipe
<johnw>
that somehow myEnvFun never runs into
munch has joined #nix-darwin
pxc has joined #nix-darwin
the has joined #nix-darwin
pjan_ has joined #nix-darwin
pxc has quit [Ping timeout: 256 seconds]
the has quit [Ping timeout: 276 seconds]
pjan_ has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
pjan_ has joined #nix-darwin
pxc has joined #nix-darwin
pxc has quit [Ping timeout: 256 seconds]
angerman has joined #nix-darwin
pjan_ has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
glenn_ has quit [Remote host closed the connection]
<angerman>
anyone who could lend me a hand with nix-docker?
<angerman>
I keep hitting: error: a ‘x86_64-linux’ is required to build ‘/nix/store/ql6frh48fw1l7clqlpva9yxzn5ji8nwi-hello-2.10.drv’, but I am a ‘x86_64-darwin’
<LnL>
that usually happens when rebuild-remote isn't working
<angerman>
LnL: how would I debug that?
<LnL>
it's a bit finicky since there are a lot of variables that influence what you need to do
<LnL>
what's the output of nix-info?
zzamboni has joined #nix-darwin
glenn_ has quit [Ping timeout: 255 seconds]
zzamboni has quit [Client Quit]
glenn_ has joined #nix-darwin
<angerman>
LnL: sorry had to help a tiny human shower.
<angerman>
`remote-system.conf` has `nix-docker x86_64-linux /etc/nix/docker_rsa 4`, `/etc/nix/machines` has `root@nix-docker x86_64-linux /etc/nix/docker_rsa 8 1 big-parallel`
<LnL>
notice the EnvironmentVariables part
<LnL>
so either do that yourself or enable the services.nix-daemon.enable option in your config
<angerman>
LnL: ok let me check.
<angerman>
LnL: btw, maybe this is related "This will link the system profile to /run/current-system. You have to create /run or symlink it to private/var/run. If you use a symlink, you'll probably also want to add services.activate-system.enable = true; to your configuration." (from the nix-darwin README). So if /run is a symlink, I need to set services.active-system.enable = true; I supposes?
<LnL>
yeah, but it's enabled by default
<angerman>
hmm I don't have those env variables in my daemon config.