In my comparison document with Debian, I use this versioned link to compare to Debian unstable ; but it means I have to update it when a new version is available. Would it be possible to provide a
PackageTable-latest.csv linking to the actual latest version, so I could always compare to that?
how is "latest" defined here? Latest in terms of Coq Platform releases, or stuff that is in the Coq Platform repo (or the Coq opam repo)?
in my view, what happens is basically that releases of packages are constantly streaming into the Coq opam archive, and then there is a curation process of picking package versions that end up in a Platform release. This curation process is not always incremental/atomic, e.g., a bunch of package versions could be added at some instant, removed/replaced the next, and everything only stabilizes definitively with the Platform release.
(in practice, some releases may not even reach the Coq opam archive until later, they might only exist as Git repo tags)
Well, I'm just using the file to compare how far from the "Coq platform" I am in my Debian packaging work
sure, I understand the motivation, but what I'm saying is that the Coq Platform "actual latest version" of packages is seemingly not defined, except for by the latest Platform release
Well, then would it be possible to let
-latest point to that Platform release?
what might make sense is to have a symlink like
PackageTable~recommended.csv which points to the package table for the recommeded Coq version of a Platform release (e.g., to
PackageTable~8.15~2022.04.csv for the latest release)
this would be consistent with how package tables are described in the notes for the latest release
until a symlink is added, one can at least use the following "algorithm" for finding the "latest" package list:
Well, I'm using a script to update that page ; a script doesn't load a page and read it...
@Julien Puydt : all the package lists are names by specific Coq Platform versions, and adding a latest would be confusing IMHO, but for sure I can add an additional file "metainfo" which contains whatever meta information you need.
E.g. there is always a "recommended" pick, and I an state in the metainfo file which pick is the recommended pick.
@Michael Soegtrop I think what Julien is looking for is a predictable file name for the "recommended" package list
so my suggestion is that you could add a symlink in the repo in a release, for the latest release you could have the following symlink:
PackageTable~recommended.csv -> PackageTable~8.15~2022.04.csv
I got that, but I don't want to do this.
the problem with just having it in the README is that there is no way to programmatically find it without parsing text
That's why I suggested to have a metainfo file, which provides such information in a wax convenient to shell and python.
One can of course encode such metainformation in symlinks as well, but I find it not so obvious.
OK, I guess as that's fine as long as these metainfo files can be read in a predictable way
Last updated: Jun 03 2023 at 03:01 UTC