| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Adds a new second argument, `where`, a string which indicates places
to search for the module.
If `where` contains "l", it will search using the LuaRocks loader; if it
contains "p", it will look in the filesystem using package.path and
package.cpath. You can use both at the same time.
If successful, it will return four values.
* If found using the LuaRocks loader, it will return:
* filename of the module (eg. "/usr/local/lib/lua/5.1/socket/core.so"),
* rock name
* rock version
* "l" to indicate the match comes from the loader.
* If found scanning package.path and package.cpath, it will return:
* filename of the module (eg. "/usr/local/lib/lua/5.1/socket/core.so"),
* "path" or "cpath"
* nil
* "p" to indicate the match comes from scanning package.path and cpath.
If unsuccessful, nothing is returned.
|
| |
|
| |
|
|
|
|
|
|
| |
Also, declare Unix version of current_user in
luarocks.fs.unix.tools, so that the pure-Lua version
based on LuaPosix takes precedence when available.
|
| |
|
| |
|
|
|
|
|
|
| |
Use a small fixture instead to test the regression for sailorproject/sailor#138
Sailor was the largest rock downloaded by the test suite, so
this should improve download times.
|
|
|
|
|
|
|
|
| |
We only used the rockspec in testing, but since the app it refers
to is GPL-3, it could cause confusion among users, so let's just
drop it from the test suite.
Closes #1387.
|
| |
|
| |
|
|
|
|
|
|
|
| |
* fix deployment on non-wrapped binaries
Fixes #1374.
* Do not add .bat extension inside win32.wrap_script
|
| |
|
|
|
|
|
| |
upload: support uploading pre-packaged .src.rock files
Co-authored-by: daurnimator <quae@daurnimator.com>
|
| |
|
|
|
|
|
|
| |
* Added prepare flag in test command
* Added test for prepare flag in spec/test_spec.lua
Fixes #1303
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
Ensure that `luarocks` fails if an installation does not successfully
deploy all files registered in the `rock_manifest`.
See #1276.
|
| |
|
| |
|
|
|
|
| |
Test case for issue reported at https://github.com/Kong/kong/issues/5017
|
| |
|
|
|
|
|
|
|
| |
This is done to support Windows. Unix handles quoting at the shell level.
While quotes are technically valid as part of Unix names, I don't expect this pathological case to be something we need to support.
Closes #1173.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Regression introduced in
https://github.com/luarocks/luarocks/commit/65c417e0ecda55f44c691df032163a8c08f0b52a
Thanks to @lhemkendreis for the detailed description and suggested
fix, which was applied here!
Added a regression test which exercises dependency matching.
Closes #1175.
|
| |
|
|
|
|
| |
Closes #1156.
|
| |
|
| |
|
|
|
|
| |
Fixes #1141
|
|
|
|
| |
Fixes #1147.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This adds support for pinning dependencies in projects and rocks:
* Adds a new flag called `--pin` which creates a `luarocks.lock`
when building a rock with `luarocks build` or `luarocks make`.
This lock file contains the exact version numbers of every
direct or indirect dependency of the rock (in other words,
it is the transitive closure of the dependencies.)
For `make`, the `luarocks.lock` file is created in the current
directory.
The lock file is also installed as part of the rock in
its metadata directory alongside its rockspec.
When using `--pin`, if a lock file already exists, it is
ignored and overwritten.
* When building a rock with `luarocks make`, if there is a
`luarocks.lock` file in the current directory, the exact
versions specified there will be used for resolving dependencies.
* When building a rock with `luarocks build`, if there is a
`luarocks.lock` file in root of its sources, the exact
versions specified there will be used for resolving dependencies.
* When installing a `.rock` file with `luarocks install`, if the
rock contains a `luarocks.lock` file (i.e., if its dependencies
were pinned with `--pin` when the rock was built), the exact
versions specified there will be used for resolving dependencies.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
* Support make --no-doc
* Add test for make --no-doc
|
| |
|
|
|
|
| |
See #1070.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
The `--branch` flag is optional and takes a string argument.
The `--branch` flag does not make sense for `luarocks make` because
it does not fetch sources, it builds/installs based on whatever is
in the current directory.
This also adds tests that verify the behavior, but these don't
run in Travis CI because of issues running a Git daemon there.
They were verified locally.
|
| |
|
| |
|