Re: Updating lang/LuaJIT2

[Greg Troxel <gdt%lexort.com@localhost>]

"J. Lewis Muir" <jlmuir%imca-cat.org@localhost> writes:

> On 04/03, Malte Dehling wrote:
>> Upstream switched to a rolling release model, which means
>> 
>> - v2.0.5 is the last tagged release and there won't be any new ones
>> - the current version is now v2.0.X, where X is the unix timestamp of
>>   the latest commit in the v2.0 branch (this timestamp is automatically
>>   placed in a file .relver in the root of the source archive.)
>
> Hi, Malte!
>
> Maybe X as 5 for the last tagged release and then followed by ".N"
> where N is the date in the form YYYYMMDD would be better?  When I see
> 1710087801, I have no idea what version that corresponds to.  But when I
> see 20240403, I immediately know approximately what version it is.
>
> Another approach that is more exact is 2.0.5.N where N is the number of
> commits to the VCS since the 2.0.5 tag.  This is described in
>
>   https://www.netbsd.org/docs/pkgsrc/fixes.html#build.fetch.github
>
> which was proposed by Jason Bacon in
>
>   https://mail-index.netbsd.org/tech-pkg/2020/05/19/msg023187.html

Good points, but if upstream is using 2.0.X where X is unix timestamp,
there is a very strong presumption to just use their numbers, whether or
not they are aesthetically pleasing.  IMHO us departing from
upstream causes confusion.