Honestly I'm not willing to pointlessly spend hours configuring packages. The Coq Platform is a really attractive way to quickly install all the packages I'd need. But... I'm not willing to spend CPU cycles compiling packages either. And the Snap distribution, I don't like Snap for a multitude of reasons. Sandboxing not well thought out, snaps are always mysteriously slower and especially, it always takes centuries to download a package! APT downloads are fast but Snap downloads are always slow. Do you have an alternative way to install the Coq Platform without having to compile the world on my machine?
I think it's unlikely there will be any other binary installers than the existing ones for the foreseeable future. But the Platform scripts don't force you to install the whole Platform, you can install "base level" (Coq and Dune) or "IDE level" (base level and CoqIDE). Even the "full level" leaves out some packages that take a long time to install, like CompCert and VST.
@Huỳnh Trần Khanh : there are also Debian packages for most packages in Coq Platform and we try to keep the versions in sync as much as possible.
Here is an overview which compares what is in Coq Platform and in Debian. Maybe we should mention this in the Coq Platform readme.
https://people.debian.org/~jpuydt/coq_platform.html
Other binary installers are planned but IMHO a prerequisite would be that .VO files are platform independent, at least for all 64 bit platforms. I don't want to keep platform specific variants of VO files.
This topic was moved here from #Coq users > Alternative way to install Coq Platform by Karl Palmskog.
We're in a freeze so I don't think I'll be able to put 8.17 as soon as I would like, but Coq 8.16.1 is in Debian since it was published.
PS: where do you see I have two accounts? I'll indeed want to delete one...
@Julien Puydt : ah yes, sorry - the list is outdated on the Coq Platform side - not the Debian side. Can you please update the Coq Platform side of it?
@Karl Palmskog I see only one of me, online when I type @Jul
@Michael Soegtrop I updated my page, but I'm not sure that's what you wanted
@Julien Puydt : Coq Platform is 8.16.1 - your page lists 8.15.2. There was a release recently (sorry, I should have pinged you).
@Michael Soegtrop I'm using this link, what is the new one?
@Karl Palmskog Ah, indeed: it's @Julien Puydt I should delete.
I think I found the new one ; I updated my page
@Julien Puydt : thanks for your efforts to provide Coq / Coq Platform as Debian packages! The package lists are usually available quite a bit before the final release. Do you want to get involved early in the package list creation? I don't expect many updates for the 2023.03 release, though.
I created (https://github.com/coq/platform/issues/323) to mention this in the Coq Platform Linux readme.
Well, as I said Debian is in a freeze now, so I won't be able to upload to the main archive anytime soon. [I'll still update my packages in their repositories and locally though!]
Bad link, it was the previous version ; here is the latest.
@Julien Puydt : what I mean is that when I inform you as early as possible that e.g. packages are added, we could fill the timeline better.
Ah, yes. For example coqword and coq-itauto -- I could probably have packaged them if I had known sooner.
What does it mean for aac-tactics to be at version 8.17.0 when Coq is only at version 8.16.1? AFAIK, AAC Tactics is never compatible with more than one version of Coq at once.
hmm, AAC Tactics 8.17.0 is only packaged in extra-dev
for opam, with requirements on 8.17 only. Did it get packaged in Debian?
it occasionally happens that AAC Tactics is compatible across Coq major versions, but this is not at all supported by the maintainer (me), and I'd prefer if packagers didn't do cross-compatible versions, e.g., both compatible with Coq 8.16 and 8.17
Well, it built and passed tests, so I uploaded it... there are other packages where a 8.17-compatible version was released but wasn't compatible, so I didn't upload.
I guess AAC Tactics could mechanize that intention by adding to its build
coqc --version | grep -q '8.16' || { echo "Unsupported Coq version"; exit 1; }
I wonder how much documentation would be needed to discourage (other) maintainers effectively from patching this out?
To be clear, if you detect any cynicism, that's not directed at you Julien
Well, indeed now I see the opam says coq >= 8.17, but as I said, I just tried to compile and load and it seems to just work.
It's very likely that if it builds it works. But this is completely untested.
(I mean, beyond whatever automatic tests there are.)
In any case I would recommend to use for all packages with a Coq version in the version the version matching Coq. These should be updated together.
if packaging becomes incongruent with maintainer intention, I guess we have to detect and act on various ENV variables and other commands to prevent this [unsupported builds]
as far as I'm concerned, the opam package in released
expresses what is actually supported
Last updated: Jun 03 2023 at 05:01 UTC