-
-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix cargo missing in dev env #51
Conversation
Ah strange. I don't have it installed globally either. In my forked copy of this repo, in older branches, I have cargo so it's coming from somewhere else in the derivation somehow. |
Isn't it coming from |
lazyDerivation ended up filtering out .nativeBuildInputs and co., which mkShell's inputsFrom relies on to figure out what to use for the environment..
Figured it out, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think lazyDerivation
is doing too much for us. The promise of being less messy now seems mostly untrue. This is more code and less easy to understand than the simple exposure of the original derivation.
Yeah agreed 馃槄 Maybe let's just not bother trying to make I'll update it shortly |
The lazyDerivation part to try to make it less messy ends up just making the code messy instead, let's just drop it and not worry about making `nix-build` without arguments work. Instead `nix-build -A build` works, and this also keeps the resulting attribute set cleaner in general.
That's what they are :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, let's do this.
No idea how I didn't notice it missing before..Must've come from somewhere else 馃しTurns out
lazyDerivation
(added in 3f361a4) ended up filtering out .nativeBuildInputs and co., which mkShell's inputsFrom relies on to figure out what to use for the environment.. 馃う