-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Make outputHashAlgo
accept "nar"
, stay in sync
#10021
Conversation
c21f04d
to
9d246ff
Compare
9d246ff
to
08d293a
Compare
if (s == "recursive") { | ||
// back compat, new name is "nar" | ||
ingestionMethod = FileIngestionMethod::Recursive; |
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.
Don't we instead want to accept `recursive as a file ingestion method for consistency?
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 am not sure what you mean, I think change ContentAddressMethod::parse
so this one is accepted everywhere (e.g. the new CLI too)?
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.
Yes, that's what I meant
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 forget whether we discussed this before, but I do want to over time steer people to the new name (which is clearer) in the new CLI.
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.
(Also with git support, which I hope to merge very soon, NAR isn't the only "recursive" format anyways.)
b84755a
to
1eb4c55
Compare
1eb4c55
to
38a6c40
Compare
38a6c40
to
feb993d
Compare
Discussed during the Nix maintainers meeting on 2024-02-28.
|
This pull request has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/2024-02-28-nix-team-meeting-129/40499/1 |
feb993d
to
504b74f
Compare
504b74f
to
ef055f4
Compare
This was part of approved PR NixOS#10021. Unfortunately that one is stalled on a peculiar Linux test timeout, so trying to get bits of it merged first to bisect failure.
ef055f4
to
f96cb57
Compare
This was part of approved PR #10021. Unfortunately that one is stalled on a peculiar Linux test timeout, so trying to get bits of it merged first to bisect failure.
Now that we have a few things identifying content address methods by name, we should be consistent about it. Move up the `parseHashAlgoOpt` for tidiness too. Discussed this change for consistency's sake as part of NixOS#8876 Co-authored-by: Eelco Dolstra <edolstra@gmail.com>
f96cb57
to
93d68e1
Compare
This would be a case where a release note becomes more valuable over time. |
Motivation
Now that we have a few things identifying content address methods by name, we should be consistent about it.
Move up the
parseHashAlgoOpt
for tidiness too.Context
Discussed this change for consistency's sake as part of #8876
Priorities and Process
Add 👍 to pull requests you find important.
The Nix maintainer team uses a GitHub project board to schedule and track reviews.