| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| | |
| |
| |
| |
| | |
`repo` sometimes means root dir and sometimes means rock dir.
At least do not reuse the same variable for both.
|
| | |
| |
| |
| |
| | |
Do not accept a hook function to call after storing results.
Simply call it on the outside after calling store_results.
|
| | |
| |
| |
| |
| |
| | |
Instead of passing a function and its arguments to a helper
function for it to call it, make a copy of result, and return it,
call the function on the outer level and pass the result to helper.
|
| |/
|
|
|
|
|
|
|
|
| |
To get all installed versions of a package using deps_mode,
instead of deeply merging all manifests of corresponding trees,
shallowly merge only tables related to that package.
This affects speed of manifest manipulation and dependency resolution.
Minimal performance testing suggests 3x-4x speed-up on reinstallation
of a package using `luarocks make`.
|
| |\
| |
| | |
Fix absolute path detection on Windows
|
| | |
| |
| |
| |
| |
| | |
Do not use "^[%.a-zA-Z]?:?[\\/]" as a pattern when checking if
a path is absolute on Windows. Check if there is a
directory separator after an optional drive letter instead.
|
| | | |
|
| |\| |
|
| | |
| |
| |
| | |
Use string replacements instead of functions in calls to gsub.
|
| | | |
|
| | | |
|
| |/
|
|
|
|
|
|
|
|
| |
This avoids in practice a problem that occurs in this scenario:
1. user installs Lua 5.1, gets lua and lua5.1 binaries
2. user installs LuaRocks, it detects and uses lua
3. user installs Lua 5.2, gets lua and lua5.2 binaries (lua is replaced)
4. user installs LuaRocks with --lua-version=5.2, it detects and uses lua
5. luarocks-5.1 now uses lua, which is Lua 5.2, rockspecs get passed the wrong value of $(LUA)
|
| |
|
|
|
| |
Let the user set their own custom platform entries,
but also provide fallbacks to make sure things work.
|
| | |
|
| |
|
|
|
| |
(e.g. allow it to find `lua5.1` when lua is 5.3 and only `--lua-version=5.1`
is given).
|
| |\ |
|
| | |\
| | |
| | | |
Make rock name arguments case insensitive
|
| | | | |
|
| | |/
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Internally package names are lowercased, however, rockspec may contain
a name with uppercase letters, which will be displayed by `luarocks show`.
Some commands, like `luarocks search`, `luarocks install` and `luarocks
build`, support this and convert input name to lowercase before passing
it to interanl functions.
Do the same thing in other commands accepting rock names.
|
| | | |
|
| | |
| |
| |
| |
| | |
Remove explicit reference to cygwin, and make option
available for custom environments.
|
| |/ |
|
| | |
|
| | |
|
| | |
|
| |\
| |
| | |
Fix conflict resolution
|
| | |
| |
| |
| |
| | |
When deploying script to bin/script.bat, check and back up
bin/script.bat, not bin/script.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
When deploying or deleting files, resolve conflicts purely
based on module names and command names, not file names.
Also, don't assume that in case of a conflict both packages have the
same file providing the module or command; it can be false due to binary
wrappers and `path_to_module("mod/init.lua")` == `path_to_module("mod.lua").
|
| |/ |
|
| |
|
|
| |
Same as 6639022.
|
| |
|
|
|
| |
Don't install luafilesystem 1.6.1 on Windows with Lua 5.3, it
fails.
|
| |
|
|
|
|
|
|
|
|
| |
In builtin backend, when figuring out where to install a module and
checking for special "init.lua" logic, trigger it only when
the whole basename is "init.lua", not when it merely ends with it.
Fixes incorrect installation when build.modules contains pairs like
`["kainit"] = "kainit.lua"` - the module used to go to `kainit/kainit.lua`
instead of just `kainit.lua`.
|
| |
|
|
|
|
|
| |
If `basename` is equal to `baseinfo` then, as `filename` is
`baseinfo` plus ".lua", assignment `filename = basename..".lua"`
has no effect and the if statement can be removed. Then `baseinfo`
can be removed as unused.
|
| |
|
|
|
|
|
|
| |
Similarly to repos.delete_version, it's a good idea to update
manifest immediately after altering what's deployed, even though
in this case manifest was always updated by the caller.
Also added more doc comments for repos functions.
|
| |
|
|
|
|
|
| |
This is a naive implementation of the solution suggested by @mpeterv for #268.
I'm merging this since it does produce more correct behavior,
at the cost of a performance regression. We need a function akin to
update_manifest for removing packages from a manifest.
|
| | |
|
| |\ |
|
| | |\
| | |
| | | |
Relax Lua version detection to support Ravi
|
| | |/
| |
| |
| |
| | |
Ravi has "Ravi 5.3" as _VERSION. Don't use _VERSION:sub(5) to get Lua
version, match " (5%.[123])$" instead.
|
| | |\
| | |
| | | |
Fix manif.find_{current,next}_provider returning "untracked" incorrectly
|
| | |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
`find_providers` function used by `manif.find_current_provider`
and `manif.find_next_provider` needs relative path from a directory
an installed file is deployed in (bin dir, lua dir, or lib dir) to the file.
It then uses that path as key in manifest, converting it to
module name beforehand for lua files and lib files.
It happened to leave a leading slash in this relative path for
lua and lib files. `path.path_to_module` has a workaround stripping
leading dots caused by leading slashes. However, if the file
doesn't have `.lua` extension, slashes are not converted to dots
and the workaround doesn't trigger.
The issue results in files falsely considered "untracked" and backed-up
when reinstalling a different version of a rock,
see sailorproject/sailor#138.
The fix is to use correct relative paths without leading slashes.
|
| | |\
| | |
| | | |
Fix of openssl location on TravisCI OSX build
|
| | | | |
|
| | | | |
|
| | |/ |
|
| |/ |
|
| |
|
|
| |
See #625.
|
| |
|
|
|
|
| |
Otherwise, when luarocks removes a previous version it may
end up deleting the site_config.lua file that was freshly
installed. Closes #625.
|
| |\ |
|
