New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LuaJIT: update to git v2.1 branch #36790
Conversation
The LuaJIT maintainer has not published a new version in 5 years, but he has steadily added commits to the "2.1" branch, linked below. https://repo.or.cz/luajit-2.0.git/shortlog/refs/heads/v2.1 Projects like neovim build against this branch or master due to the lack of a recent release. Furthermore, distributions such as Arch Linux and Debian Sid are building from a commit rather than a release. archlinux/svntogit-community@11473c3 https://salsa.debian.org/lua-team/luajit/-/commit/e06cbc6d2a61b253056214f5ed3f03ce661e31f9 The LuaJIT upstream maintainer has declined to cut a release, reasoning "Releases are an antiquated concept". LuaJIT/LuaJIT#665 (comment)
i think that packages should be switched from luajit to regular lua where possible for years luajit has been nothing but a poorly portable liability with a bus factor of 1 (go look at the code and you'll know why), and we should do away with it where we can neovim can use standard lua, as can a lot of things that are currently built against luajit |
also I'm like 90% sure the ppc64le patch does not apply anymore as I don't see it updated |
Maybe it can, but the devs don't seem to want to support such a setup:
Would you be willing to update it? I have no ppc(64)(le) hardware to test with. Debian appears to be using this patch: https://salsa.debian.org/lua-team/luajit/-/blob/master/debian/patches/0004-Add-ppc64-support-based-on-koriakin-GitHub-patchset.patch |
How about https://github.com/openresty/luajit2, which does have releases and is used by e.g. Homebrew as a replacement for upstream LuaJIT? |
That would solve the "bus factor" issue, at least. 😅 |
Alpine builds on OpenResty's tag release as well. |
this is dope |
This comment was marked as off-topic.
This comment was marked as off-topic.
I believe it's meant to relieve considerable burden from the project. |
I would be okay with taking the openresty fork by the way, though we would need to test if ppc32 is still broken there (or i could drop it) |
Any update on the discussion regarding this? |
I think the consensus is to switch to the openresty upstream. |
also related: neovim/neovim#17562 |
CC: @q66
The LuaJIT maintainer has not published a new version in 5 years, but he
has steadily added commits to the "2.1" branch, linked below.
https://repo.or.cz/luajit-2.0.git/shortlog/refs/heads/v2.1
Projects like neovim build against this branch or master due to the lack
of a recent release.
Furthermore, distributions such as Arch Linux and Debian Sid are
building from a commit rather than a release.
archlinux/svntogit-community@11473c3
https://salsa.debian.org/lua-team/luajit/-/commit/e06cbc6d2a61b253056214f5ed3f03ce661e31f9
The LuaJIT upstream maintainer has declined to cut a release, reasoning
"Releases are an antiquated concept".
LuaJIT/LuaJIT#665 (comment)
Testing the changes