| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
compat53 is vendored since #1757 as it is required to run luarocks with lua 5.1 or 5.2.
However, this introduced some issues as the GNUmakefile install rule places these in the same place where `luarocks install compat53` would install them. This means you get conflicts if you install the actual package:
```
Warning: /.../prefix/share/lua/5.1/compat53/init.lua is not tracked by this installation of LuaRocks. Moving it to /.../prefix/share/lua/5.1/compat53/init.lua~
Warning: /.../prefix/share/lua/5.1/compat53/module.lua is not tracked by this installation of LuaRocks. Moving it to /.../prefix/share/lua/5.1/compat53/module.lua~
Warning: /.../prefix/share/lua/5.1/compat53/file_mt.lua is not tracked by this installation of LuaRocks. Moving it to /.../prefix/share/lua/5.1/compat53/file_mt.lua~
```
It is also not ideal for linux package maintainers to include a vendored package, see: https://github.com/luarocks/luarocks/pull/1757#issuecomment-3409873412.
To solve these issues, this patchset makes the following changes:
- GNUmakefile now places the compat53 files under `luarocks/vendor/compat53` (which is added internally to the luarocks script's `package.path`). This way a user's installation of compat53 does not interfere at all with luarocks one.
- Added `--with-system-compat53` option to configure script for external packaging systems.
- Fixed install.bat's logic for deciding whether to vendor compat53, as the current script includes it for every version.
install.bat already places luarocks sources outside of LUAPATH, so that part can stay as is.
I've also inverted the version check to avoid the need for future patches like: #1850.
|
| | |
|
| |
|
|
| |
(#1825)
|
| |
|
| |
This allows copy pasting the commands easily
|
| |
|
|
| |
archive content
|
| | |
|
| | |
|
| | |
|
| |\ |
|
| |/ |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |\ |
|
| | |
| |
| |
| | |
Co-authored-by: luau-project <luau.project@gmail.com>
|
| | | |
|
| | |
| |
| |
| | |
Co-authored-by: luau-project <luau.project@gmail.com>
|
| | |
| |
| |
| |
| | |
Support Lua 5.4 and 5.5,
see https://github.com/luarocks/luarocks/pull/1832
|
| |/ |
|
| |
|
|
| |
This should fix our CI failure
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
On every tagged release of LuaRocks, there is the need to update LuaRocks version at [https://github.com/luarocks/gh-actions-luarocks/blob/22fa5618dc4ddff1fb251b3b38a0766a8c9ae47f/action.yml#L13](https://github.com/luarocks/gh-actions-luarocks/blob/22fa5618dc4ddff1fb251b3b38a0766a8c9ae47f/action.yml#L13) in the repository [https://github.com/luarocks/gh-actions-luarocks](https://github.com/luarocks/gh-actions-luarocks). Often forgotten, the default LuaRocks version on `gh-actions-luarocks` may lag behind the latest LuaRocks release.
Motivated by this comment [https://github.com/luarocks/gh-actions-luarocks/pull/7#issuecomment-2997223378](https://github.com/luarocks/gh-actions-luarocks/pull/7#issuecomment-2997223378), to address this problem, incorporating the changes on this pull request, a new workflow was created to proceed in the following manner:
1. Once a tag is pushed (in the usual format `vX.Y.Z`) on [https://github.com/luarocks/luarocks](https://github.com/luarocks/luarocks), or in a manual workflow triggered by the tag ref, a sanitization step is performed to extract `X.Y.Z` from the `vX.Y.Z` in the job `SanitizeVersion`;
2. In a subsequent job (`CreatePullRequest`), a PR is created at [https://github.com/luarocks/gh-actions-luarocks](https://github.com/luarocks/gh-actions-luarocks) replacing the outdated version by the value `X.Y.Z` extracted earlier.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
Removing this broke the behavior of some luarocks.build
plugins. LuaRocks does not have a stable public API,
but since this function was returned as part of the
function signature, we'll revert this as a deprecated
function, to be removed in LuaRocks 4.0.
Closes #1800.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |\ |
|
| |/ |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
Rockspecs can access the directory of its dependencies using variables
in the format 'foo_ROCKDIR' where 'foo' is the name of a dependency.
This is used to be able to access files of the rock like 'conf', 'docs'
and more.
|
| | |
|
| | |
|
| | |
|