Stream: SerAPI

Topic: coq-serapi versioning


view this post on Zulip Julien Puydt (Dec 15 2021 at 07:32):

Why are tags for coq-serapi looking like 8.14.0+0.14.0? I think the first part means the targeted coq version, but I prefer asking...
(I would like to package it for Debian)

view this post on Zulip Notification Bot (Dec 15 2021 at 08:40):

This topic was moved here from #Coq devs & plugin devs > coq-serapi versioning by Karl Palmskog

view this post on Zulip Karl Palmskog (Dec 15 2021 at 08:42):

SerAPI is completely tied to a specific major Coq version, such as 8.14, which is why the first part of the version is the Coq version it was released for.

The second part is the "internal" SerAPI version name, which indicates what protocol features and tools are delivered together with a SerAPI release. For example, there might be a version/tag 8.14.0+0.14.1 which adds some minor feature or fixes some protocol issue.

view this post on Zulip Paolo Giarrusso (Dec 15 2021 at 10:14):

Nit but why 8.14.0, if it's tied to 8.14 and can be used with Coq 8.14.1?

view this post on Zulip Karl Palmskog (Dec 15 2021 at 10:16):

well, I don't know exactly, but I think it's because it's the exact Coq version it was tested for at release time. Then due to Coq's compatibility policy it happens to work for 8.14.1 and 8.14.2, etc., but this is not guaranteed by SerAPI itself

view this post on Zulip Emilio Jesús Gallego Arias (Dec 15 2021 at 23:35):

Indeed, that's something I thought myself of moving 8.14.0 to just 8.14

view this post on Zulip Emilio Jesús Gallego Arias (Dec 15 2021 at 23:35):

but indeed that was done like this originally in case we would need a 8.14.1+foo version some day

view this post on Zulip Emilio Jesús Gallego Arias (Dec 15 2021 at 23:35):

but the idea is coq_version+serapi_version


Last updated: Feb 06 2023 at 05:03 UTC