I'm preparing elpi-1.11(.2) package and of course it breaks the last release of coq-elpi :-/
I'm about to release coq-elpi 1.4 that works with elpi 1.11.2
At least in opam, coq-elpi has a strict dependency on elpi. It is expected. I don't know which is the model of nix to handle transition of multiple packages with strict dependencies. If it is like in debian, you will have to wait until coq-elpi 1.4 is out, which is in a few days
The changes in the ML API between elpi 1.10 and 1.11 are very small, so a backport of coq-elpi 1.3 is possible, but I don't think it is worth it.
Enrico Tassi said:
At least in opam, coq-elpi has a strict dependency on elpi. It is expected. I don't know which is the model of nix to handle transition of multiple packages with strict dependencies. If it is like in debian, you will have to wait until coq-elpi 1.4 is out, which is in a few days
The policy is that both may exist, but only one is promoted (i.e. accessible via the minimum number of characters) and it is generally the most recent one with enough working dependencies (so in short, yes I will wait ;))
but I can use my nixpkgs branch + coq-elpi master to provide a shell for hb
Enrico Tassi said:
The changes in the ML API between elpi 1.10 and 1.11 are very small, so a backport of coq-elpi 1.3 is possible, but I don't think it is worth it.
Yeah don't bother
I made the tag for coq-elpi 1.4
We should make a tag on master, then merge it also in coq-master, then branch from that point a coq-v8.12 branch that will be followed by 8.12 beta, final and point releases. I should do the same for coq-elpi (I've already the tag, and it is merged in coq-master). CI should be updated accordingly, so that if we need to push a fix to coq-8.12 we can test it.
Last updated: May 28 2023 at 18:29 UTC