-
-
Notifications
You must be signed in to change notification settings - Fork 14.1k
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
ocamlPackages.elpi: use release tarball #343266
Conversation
}: | ||
|
||
let p5 = camlp5; in | ||
let camlp5 = p5.override { legacy = true; }; in | ||
|
||
let fetched = coqPackages.metaFetch ({ |
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.
@vbgl removing this will break the ability to conveniently overlay ocamlPackages.elpi in various CIs to anything else than released versions, which might be pretty unconvenient. Although I'm not sure how often we use that feature.
Cc @CohenCyril @gares ?
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.
Right. So my question is: can we use metaFetch
to download the released artifacts when available?
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 use that feature via the coq nix toolbox.
But I also need elpi to have a version number (for conditional compilation).
I hope both requirements are not in conflict.
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.
can we use
metaFetch
to download the released artifacts when available?
I don't know, but if not, maybe an option can be added?
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.
Right. So my question is: can we use
metaFetch
to download the released artifacts when available?
Sure, feel free to amend the default-fetcher
here:
https://github.com/NixOS/nixpkgs/blob/master/pkgs/build-support/coq/meta-fetch/default.nix
You can add an extra "artifact" argument (false by default?) to change the url in the github case here:
nixpkgs/pkgs/build-support/coq/meta-fetch/default.nix
Lines 38 to 39 in a11ec09
{ cond = pr != null && (match "^github.*" domain) != null; | |
out = "https://api.${domain}/repos/${owner}/${repo}/${fmt}/pull/${head pr}/head"; } |
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 use fetchurl
when you probably use fetchzip
?
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.
Ah ... sure, but I thought the uncompressed archives were compared... why is the result different?
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.
fetchurl
does not decompress: it computes the hash of the downloaded file.
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.
done: da329e4
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.
Thanks. Cherry-picked to this branch.
Update after NixOS/nixpkgs#343266
Description of changes
Released tarballs include correct version information.
Tests: coq-community/coq-nix-toolbox#266
cc @gares @proux01
Things done
nix.conf
? (See Nix manual)sandbox = relaxed
sandbox = true
nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)Add a 👍 reaction to pull requests you find important.