Skip to content

Add rockspec#92

Merged
leso-kn merged 3 commits intobastibe:masterfrom
leso-kn:luarocks
Apr 18, 2026
Merged

Add rockspec#92
leso-kn merged 3 commits intobastibe:masterfrom
leso-kn:luarocks

Conversation

@leso-kn
Copy link
Copy Markdown
Collaborator

@leso-kn leso-kn commented Oct 16, 2025

Hi :) This PR adds a package definition for LuaRocks and adds compatibility for Python 3.11+.

I took the liberty to prepare a demo rock under https://luarocks.org/modules/leso-kn/lunatic-python, so you can try out the PR from my unmerged feature branch using:

> luarocks install lunatic-python

Python can then be used from inside Lua, e.g.:

-- test.lua
local py = require 'python'
py.execute 'print("Hello from Python inside Lua!")'

In case you prefer to not include this or when it gets merged, I'll of course delete my version on luarocks.org so you can upload under the package name 'lunatic-python'.

Thanks for keeping this project up!

@leso-kn
Copy link
Copy Markdown
Collaborator Author

leso-kn commented Oct 16, 2025

Small edit: I've corrected the license field in the rockspec to LGPL-2.1, had put MIT out of habit accidentally.

@leso-kn leso-kn force-pushed the luarocks branch 2 times, most recently from 57227aa to 051efaa Compare October 16, 2025 15:19
@bastibe
Copy link
Copy Markdown
Owner

bastibe commented Jan 10, 2026

Thank you for your contribution. Is this PR ready to merge? I'm sorry to say, I don't have the time to review it myself.

@leso-kn
Copy link
Copy Markdown
Collaborator Author

leso-kn commented Jan 12, 2026

@bastibe Hey there :) I had to check again myself – yes, it is!

After merging, you can easily upload the package to luarocks.org by running:

> luarocks upload lunatic-python-scm-0.rockspec

Before you do, please ping me, so I can delete the demo rock [1] to free the name "lunatic-python"

@leso-kn
Copy link
Copy Markdown
Collaborator Author

leso-kn commented Jan 12, 2026

After merging I also suggest to create a git tag (e.g. 1.0.0), so you can upload a non-scm version to luarocks:

> luarocks new_version --dir rockspecs lunatic-python-scm-0.rockspec 1.0.0
> luarocks upload rockspecs/lunatic-python-1.0.0-1.rockspec

This will allow to install the rock directly via luarocks install lunatic-python

If you need assistance with any of that, feel free to ping me :)

@leso-kn
Copy link
Copy Markdown
Collaborator Author

leso-kn commented Jan 31, 2026

Info: Today I noticed a regression in the luarocks-Makefile regarding the Lua include path when building on Debian.

The regression is fixed with fe38122

@bastibe
Copy link
Copy Markdown
Owner

bastibe commented Apr 12, 2026

Frankly, I am no longer using this project at all, and could use help maintaining it.

@leso-kn
Copy link
Copy Markdown
Collaborator Author

leso-kn commented Apr 17, 2026

@bastibe I could offer myself as co-maintainer. I cannot guarrantee that I'll have lots of time to add new features, but I would do my best to look into PRs.

As a small-ish reference, I maintain several other lua packages.

For starters I would merge this PR and make the package installable via luarocks using the steps above :)

@leso-kn
Copy link
Copy Markdown
Collaborator Author

leso-kn commented Apr 17, 2026

If you are interested, that would be under Settings > Collaborators

@bastibe
Copy link
Copy Markdown
Owner

bastibe commented Apr 18, 2026

Thank you very much. I've sent you an invitation.

@leso-kn
Copy link
Copy Markdown
Collaborator Author

leso-kn commented Apr 18, 2026

Thanks :) Accepted! I happen to be on the computer. I'll look into merging this PR today!

@leso-kn leso-kn merged commit f060b49 into bastibe:master Apr 18, 2026
@leso-kn
Copy link
Copy Markdown
Collaborator Author

leso-kn commented Apr 18, 2026

Update @bastibe I've merged the changes.

  • Lunatic Python can now be installed via luarocks
  • I have updated the Installing section of the readme with instructions for different package managers
  • Finally, I've created a tag (v1.0) to allow changes to the master branch without breaking the version packaged on luarocks.org

If you're unhappy with any of these, just let me know or feel free to revert / change them!

From my side, this should be it for now! Should any pull-requests be opened in the future, I'll do my best to look into them if I find the time. Thanks for letting me apply these updates so far! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants