LuaJIT will fail to build in the future

[rfl890]

The creator of LuaJIT, Mike Pall, strongly recommends to use rolling releases for LuaJIT instead of the release tarballs that he provides (not for much longer, apparently):
(https://luajit.org/download.html)

LuaJIT uses rolling releases. There are no release tarballs available for download.
Please do not use obsolete versions from older tarballs or zip files. Please remove any outdated links to these downloads — these links will cease to work soon.

Currently the LuaJIT package uses one of these outdated links. It will fail to build in the future. Additionally, the version currently in use hasn't been updated for 6 years.

[classabbyamp]

we have distfile mirrors at sources.voidlinux.org

[rfl890]

I see. On another note will the package be updated to rolling releases or will it continue to stay on the current version?

[yoshiyoshyosh]

there appears to be new tags (not refs, static tags) by the format of ${version}-ROLLING that can be downloaded as a targz e.g. https://repo.or.cz/luajit-2.0.git/snapshot/refs/tags/v2.1.ROLLING.tar.gz. these tags only track from the beginning of a version's development and, simply due to the rolling release thing they have going on, won't get incremental bugfixes until a new version tag comes out and can be pointed to. they're still like, pseudo-releases though, so maybe we can point distfiles there?

if anything, getting off a 6 year old version to a 5 month old version is probably for the better

[classabbyamp]

my understanding is the tags like 2.1.ROLLING will be periodically re-tagged as a "rolling" release

[yoshiyoshyosh]

I guess if retags do happen then we can just revbump and have it still work

update: or we could bake the git show --format=%ct thing they do for the relver in the version

[github-actions]

Issues become stale 90 days after last activity and are closed 14 days after that. If this issue is still relevant bump it or assign it.