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
coqPackages_8_16.coq-lsp: init at 0.1.6+8.16 #213397
Conversation
It seems that version |
Thank you for reviewing. I moved the expression to |
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.
LGTM
inherit version; | ||
defaultVersion = with lib.versions; lib.switch coq.coq-version [ | ||
{ case = range "8.16" "8.17"; out = "0.1.4+v8.16"; } | ||
] null; |
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.
this lsp won't work on Coq older than 8.16 I take it
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.
Folks thanks for this PR, for Coq 8.17 you need a 8.17 specific tree, unfortunately the Coq API we use is not stable between versions.
Tag for 8.17 is 0.1.4+v8.17
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.
Then it should be possible to use "0.1.4+v${coq.coq-version}"
, that's the beauty about a functional language
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.
It should yes! Something that has been brought to my attention is whether the branch names should be +v8.16
or +8.16
, it seems the lastest scheme is the standard (including in some of my packages) so I'm unsure if I should tweak the tag names for the upcoming releases (and add the corresponding aliases back)
Any advice you folks have here as to easy packaging is most welcome.
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.
It would be preferable, as I think the v messes up the reverse package name parser (e.g. when doing nix-env -e coq-lsp
it tries to strip the version suffix)
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 @Thesola10 , so to confirm 0.1.4+8.16
is more Nix-friendly than 0.1.4+v8.16
?
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.
You might not need to change your actual tagging scheme -- since mkDerivation
accepts arbitrary key/values, you could define a packageVersion = "0.1.4"
and compose the derivation's version
as "${packageVersion}+${coq.coq-version}"
and the source tag as "${packageVersion}+v${coq.coq-version}"
Hi, coq-lsp 0.1.5 has been released. Would we be able to bump the version here? |
Also we have a flake capable of building that has been merged, does that help things? |
Hi @Alizter I'd suggest packaging 0.1.6 which is just out. coq-lsp is a standard dune package (an vscode extension) so as long as Coq kinda works things should be fine, it also obeys |
Thank you for your reviews. I updated the expression to |
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 did not test, but it looks good.
Great @marsam , thank you very much! We've detected a bug specific to 8.16 support (we usually test in 8.17), it is a small bug but annoying, we put a new https://github.com/ejgallego/coq-lsp/releases/tag/0.1.6.1%2B8.16 tag with the 8.16 specific fix. |
Updated to |
Description of changes
Add https://github.com/ejgallego/coq-lsp
Things done
sandbox = true
set innix.conf
? (See Nix manual)nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)nixos/doc/manual/md-to-db.sh
to update generated release notes