| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |\ |
|
| | |\
| | |
| | | |
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.
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
This avoids sprinkling the luarocks.deps dependency everywhere.
|
| | | |
|
| |\| |
|
| | |
| |
| |
| |
| | |
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.
|
| | |\ |
|
| | | |\
| | | |
| | | | |
Don't use coroutines in util.sortedpairs
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
util.sortedpairs is used in luarocks loader since @6dc745a.
Openresty does not like coroutines being used from inside `require`,
resulting in "attempt to yield across C-call boundary" error.
New version of util.sortedpairs uses a prepared array of ordered keys
instead of coroutines.
Ref #620.
|
| | | |/ |
|
| | |/ |
|
| | |\ |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Older versions of LuaRocks (e.g. 2.1.0) install script wrappers
that assume that `luarocks.loader` is available in the global
namespace (this is from the module() era). This workaround detects
this (because site_config.lua files written by these old versions
use module(), and therefore create a `luarocks` global.
To reproduce this issue, make a clean install of LuaRocks 2.1.0,
then run `luarocks install luarocks`. Installation succeds,
but running `luarocks` produces `attempt to index field 'loader'
(a nil value)`.
Bug reported by @tomasguisasola.
|
| | |/ |
|
| | | |
|
