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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Accept realised store paths as input #47
Conversation
The tool still accepts `.drv` files as input but also realised (built) paths. It's possible to ask for the derivation corresponding to a store path with nix-store -qd store-path Nix also takes care of following symbolic links. The motivation is being able to easily compare a newly built system with the currently running system: nix-diff /run/current-system $result
nix-diff.cabal
Outdated
@@ -30,6 +30,7 @@ executable nix-diff | |||
, text >= 1.2 && < 1.3 | |||
, unix < 2.8 | |||
, vector >= 0.12 && < 0.13 | |||
, process |
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.
What would be the reasonable version constraints ? Just < 1.7
?
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, < 1.7
is what I recommend
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.
Following the same logic, I added < 1.5
for filepath.
Co-authored-by: Sandro <sandro.jaeckel@gmail.com> Co-authored-by: Gabriella Gonzalez <Gabriel439@gmail.com>
for filepath and process.
Thank you for contributing this! 🙂 |
The tool still accepts
.drv
files as input but also realised (built) paths.It's possible to ask for the derivation corresponding to a store path with
Nix also takes care of following symbolic links.
The motivation is being able to easily compare a newly built system with the currently running system: