feat: allow nixpkgs package definitions #135
Open
Conversation
This file contains hidden or 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
Contributor
Author
|
@zimbatm Can you review this, please? I think this is a great addition for compatibility with nixpkgs |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
I found it quite annoying recently that it's not possible to copy a Nix package from nixpkgs directly into the
packages/directory because Blueprint only accepts the custom argument attributes.Nixpkgs defines packages in a way that the function argument attrset is direct subset of nixpkgs which Blueprint currently doesn't support. I found the fix for this quite easy.
To test this you can add
hello.nixto yourpackages/. And rungit add packages/hello.nix && nix build .#hello