| 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.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Fixes #1638
This Makefile only supports single-job execution and is known to have
race conditions that will fail if targets are run in parallel jobs. With
the proliferation of cores, more and more distributions and host
environments are setting default make flags to run jobs in parallel by
default. We can't do anything about this for old versions of GNU Make,
but for 4.3+ we can actually reset the flag ourselves to only run
a single job so targets run in serial order.
|
| | |
|
| |
|
|
| |
Fixes #1639.
|
| |
|
|
| |
Fixes #1038.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This reverts the removal from e9215f139be7afa3af116a2039594362e4f1f2be
but keeps the addition of the custom package loader as that is
a more robust approach.
I'm not a super fan of this approach because in a cross-compiling
scenario it does leak the host package.path into the output of commands
such as `luarocks path` and building the `bin` wrappers, but at least
it is less broken than the 3.2.0 behavior, as reported by @fperrad in
issue #1070.
|
| | |
|
| |
|
|
| |
As originally suggested by @blueyed in #1043.
|
| | |
|
| |
|
|
| |
See https://github.com/luarocks/luarocks/issues/952#issuecomment-449966779
|
| |
|
|
| |
Fixes #889.
|
| |
|
|
|
| |
As a convenience to distro maintainers who may want to distribute
multiple versions of the LuaRocks configuration.
|
| |
|
|
|
|
| |
* Do not set again variables that were set in config.unix
* Do not re-detect the Lua version after configure already did it
* Remove --luarocksconfdir, use --sysconfdir only
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|