Re: On frama-c's debian/watch

[Mehdi Dogguy <mehdi@dogguy.org>]

Hi,

Early versions of FramaC were snapshots with dates and codenames. There were no version numbers back then (the date was the only reliable number we've got). At some, they dropped the dates and assigned version numbers to codenames and kept going with them.

One needs to check with them that this schema is stable and not subject to changes in the foreseable future to avoid epoch'ing twice though.

Regards,

Le 28 juillet 2022 09:21:15 GMT+02:00, "Stéphane Glondu" <steph@glondu.net> a écrit :

Le 22/07/2022 à 20:19, julien.puydt@gmail.com a écrit :
upstream had modified their site, so I complained:

  https://git.frama-c.com/pub/frama-c/-/issues/2622

and upstream pretty quickly provided a new page ; except that I don't
get how from upstream 25.0-Manganese we got a Debian version 20220511-
manganese-1.3 !

With d/watch being:

version=4
https://frama-c.com/html/direct-source-distributions.html .*/frama-c-
([0-9]{2}\.[0-9]-[a-zA-Z]+)\.tar\.gz

then uscan -v lists the upstream versions in a reasonable order.

What can we do to improve things?

I was also suprised when I looked at frama-c'v versioning.

I don't know why date-based versions were chosen.

If I were in charge, I would add an epoch et start using upstream
version numbers.


Cheers,

-- 
Stéphane

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.