[Slackbuilds-users] Question about rolling source packages and version numbers

[Jeremy Hansen]

On Mon, Jan 8, 2024, 6:44 PM Erik Falor <ewfalor at gmail.com> wrote:

> Hi all,
>
> LuaJIT uses rolling releases. There are no release tarballs available for
> download.  Instead of manual increments for each release, the build process
> uses the POSIX time stamp of the latest commit as the release number of the
> semantic version.
>
> The full version number is in the format `$major.$minor.$timestamp`.  For
> instance, the latest SlackBuild I'm preparing has this version number:
> 2.1.1703358377.
>
> One can download a tarball of a specific commit from their GitHub
> mirror[1].
> Because they aren't given tags with the version number, you have to refer
> to
> them by the commit ID:
>
>
> https://github.com/LuaJIT/LuaJIT/archive/c525bcb9024510cad9e170e12b6209aedb330f83/LuaJIT-c525bcb9024510cad9e170e12b6209aedb330f83.tar.gz
>
> Of course, this means that the tarball expands to a subdirectory that
> contains
> the commit ID instead of a version number in its name.
>
> I can reconcile this by adding the $REVISION variable to the SlackBuild:
>
> PRGNAM=luajit
> REVISION=${REVISION:-c525bcb9024510cad9e170e12b6209aedb330f83}
> VERSION=${VERSION:-2.1.1703358377}
>
> Is this a satisfactory solution, or has this problem been solved in a
> better way
> by another maintainer?
>
>
> [1] https://github.com/LuaJIT/LuaJIT
>
> --
> Erik Falor
>

I do something similar with picard-plugins [1]. They don't do formal
releases, just I just grab the commit that was current at the time of the
version of picard I'm packaging when it was released.

I don't think there is a formalized process to handle different versions
within the source name and folder structure. I like using SRCNAM, but
REVISION works well in your case as well.

[1] https://slackbuilds.org/repository/15.0/multimedia/picard-plugins/

Jeremy

>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240108/86500f58/attachment-0001.htm>