Skip to content
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 2.1.1710088188 #2000

Merged
merged 1 commit into from
Apr 29, 2024

Conversation

nazar-stasiv
Copy link
Contributor

Summary

Test Plan

  • luajit -v

Checklist

  • Package was built and tested against unstable

@nazar-stasiv
Copy link
Contributor Author

Since recently luajit doesn't release tarballs, and applies rolling release policy where version is major.minor.timestamp.

**Summary**
- Bugfix release
- [changelog](https://repo.or.cz/luajit-2.0.git/shortlog)

**Test Plan**
- rlwrap luajit

**Checklist**
- [X] Package was built and tested against unstable
Copy link
Member

@davidjharder davidjharder left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the update.

What would a sane plan look like to keep luajit updated without updating every time the authors make a commit?

@davidjharder davidjharder merged commit c84d7d3 into getsolus:main Apr 29, 2024
1 check passed
@nazar-stasiv
Copy link
Contributor Author

What would a sane plan look like to keep luajit updated without updating every time the authors make a commit?

You assume this is a development branch, right? This is wrong. Because for 2.1 release, which is in its bugfix phase, there are only occasional merges. Only difference is
instead of tags, luajit uses branch.

@davidjharder
Copy link
Member

That makes more sense, thanks

@nazar-stasiv nazar-stasiv deleted the update_luajit branch May 4, 2024 19:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

3 participants