Use nativeBuildInputs for nix-shell #2504
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Now the nix-shell will generate a nix expression that looks like this:
with import <nixpkgs> {};
runCommand "shell" {
nativeBuildInputs = [
(...)
(...)
(...)
];
}
from
$ nix-shell --packages ... ... ...
Fixes the issue described in NixOS/nixpkgs#38657.
|
Any chance of this getting some love? |
|
Some cases could also screw this up, however. For instance in some cases you want to treat your dependencies as libraries (for zlib, libsystemd, etc.). For now it is probably safest to leave the behavior as is (with -p implying buildInputs). |
|
I marked this as stale due to inactivity. → More info |
|
I closed this issue due to inactivity. → More info |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Now the nix-shell will generate a nix expression that looks like this:
from
$ nix-shell --packages ... ... ...
Fixes the issue described in NixOS/nixpkgs#38657.