nixstore: Nix expression for generating a nixpkgs index #885
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
This expression generates a JSON blob containing the metadata for every derivation in nixpkgs, similar to that of hydra's `packages.json`. It differs in that it also includes the store path for each package and contains the system that generated the index. The system field lets us know which packages can actually be evaluated for a given system, which tends to differ from the systems that claim to be supported in the metadata. This isn't used anywhere yet, but it can be manually called as a script to generate the JSON for prototyping or debugging.
mikeland73
approved these changes
Apr 10, 2023
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.
This expression generates a JSON blob containing the metadata for every derivation in nixpkgs, similar to that of hydra's
packages.json. It differs in that it also includes the store path for each package and contains the system that generated the index. The system field lets us know which packages can actually be evaluated for a given system, which tends to differ from the systems that claim to be supported in the metadata.This isn't used anywhere yet, but it can be manually called as a script to generate the JSON for prototyping or debugging.