<Joestar79>
it builds just fine but as soon as it print to the console installing, I got this error message: mkdir: cannot create directory '/share': Read-only file system
<__monty__>
You usually want 'super.callPackage' not 'self.callPackage', fyi.
<Joestar79>
__monty__ thank you, changed that but I still get the same error
<Joestar79>
should I just create that /share dir before darwin-rebuild switch ? if yes, I'm not sure where exactly though
<__monty__>
Are you on Catalina? This sounds to me like a consequence of the locked down /.
<Joestar79>
unfortunately yes, I'm on Catalina
<Joestar79>
any ideas or possible workarounds?
<__monty__>
I'm not familiar with catalina no. I'm sure someone'll be able to help. Can't you make it use a different directory?
<Joestar79>
I really have no clue
<Joestar79>
let me check the .nix files I checked out and see if they mention /share anywhere
<LnL>
specifying eg. outputs = [ "bin" "out" ]; would also work
<LnL>
by default nix packages only are a single output out where the build can write to
<LnL>
but sometimes it's useful to split a package up into multiple parts so a user using the binary doesn't have to pull in all the headers, etc.
<LnL>
so in that case the build gets 2 random store paths it can write to instead of just the one
<Joestar79>
hmm I tried using $out instead of $bin and then using outputs = [ "bin" "out" ]; but it still fails
<Joestar79>
this is the error: /nix/store/yd7798v1xb0hf07jrs3y5ypjj37nnylg-stdenv-darwin/setup: line 93: /nix/store/f55nmls9jldsbwxxaw7v5aamifqzpag8-helm-2.15.1-bin/bin/helm: No such file or directory
<Joestar79>
I used $bin and added: outputs = [ "bin" "out" ];
<Joestar79>
but also just renaming $bin to $out fails as well
<LnL>
I'm guessing just adding bin isn't enough because the build isn't moving the binary there anymore either
<Joestar79>
I installed it and tried to build the example, but I'm getting: error: a 'x86_64-linux' with features {} is required to build '/nix/store/0w6pl11qhy3qgn7z0s5gxd51y8jnsvpy-hello-1592237239.drv', but I am a 'x86_64-darwin' with features {benchmark, big-parallel, nixos-test}
<Joestar79>
I ran this: nix-build /Users/stondo/.cache/nix-linuxkit-builder/example.nix
<Joestar79>
if I edit the file and put darwin instead of linux, it works
<Joestar79>
but still how does help with hyperkit not being on nixpkgs?
<LnL>
that's a functional hyperkit build so you can base it on that
<Joestar79>
ah ok, the .nix I'm gonna create will use that as a builder, right?
<LnL>
you can probably copy that folder next to xhyve and add an entry for it to all-packages.nix
<Joestar79>
I've been using Nix for less than a week, so I'm sorry if I'm slow to understand the help you guys are giving me. But I do appreciate a lot all of the info u guys are sharing, thanks!
<__monty__>
Fwiw, reading the manuals front to back does help clear many things up.
<LnL>
maybe, but to be fair that's not really 'reading' material
<LnL>
the manual is mostly a reference guide
<__monty__>
I didn't make any enjoyability claims : )
<LnL>
and the nix pills are an intermediate introduction to how the internals stdenv
<__monty__>
I'm not familiar with the use of stdenv as a verb.
Chiliparrot has quit [Quit: My iMac has gone to sleep. ZZZzzz…]
Chiliparrot has joined #nix-darwin
Chiliparrot has quit [Client Quit]
philr_ has joined #nix-darwin
__monty__ has quit [Quit: leaving]
<mitchellh>
QQ: I'm setting `environment.shells` and it is not having any effect. Where should I debug? (The exact value is `environment.shells = [ pkgs.fish ];`
<mitchellh>
nvm
<mitchellh>
> warning: not linking environment.etc."shells" because /etc/shells exists, skipping...
<{^_^}>
error: syntax error, unexpected ',', expecting ')', at (string):316:73
<mitchellh>
obviously
<LnL>
yeah, it's a bit (overly?) careful not to mess up system files
<LnL>
I'm also not entirely sure how well certain thinks like that deal with potentially having a broken symlink before the volume is mounted