Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Let LuaRocks find LUA_LIBDIR and LUA_INCDIR by itself | Hisham Muhammad | 2018-07-01 | 1 | -4/+4 |
| | |||||
* | Tests: config: no need for special-casing Windows | Hisham Muhammad | 2018-07-01 | 1 | -36/+20 |
| | |||||
* | cfg, cmd: major reorganization | Hisham Muhammad | 2018-07-01 | 1 | -8/+8 |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * `--lua-dir` flag, specifying a prefix for the Lua installation to be used. This reconfigures LuaRocks entirely, including allowing a LuaRocks which is itself running using one Lua 5.x version to manage packages for a different Lua 5.y version. The resulting configuration can be checked with `luarocks config --lua-dir=<path>`. * requiring `luarocks.core.cfg` no longer has side-effects * configuration now needs to be initialized with `cfg.init([lua_data])`, where `lua_data` is a table with the configuration of the VM: * `lua_version` - e.g. `"5.3"` * `luajit_version` - e.g. `"2.1.0-beta3"` * `lua_interpreter` - e.g. `"lua5.3"` * `lua_bindir` - e.g. `"/usr/local/bin"` * `lua_libdir` - e.g. `"/usr/local/lib"` * `lua_incdir` - e.g. `"/usr/local/include/lua-5.3"` * `cfg.init` can be called multiple times, reconfiguring the global state. This is important since `luarocks.loader` now calls it, and the `--lua-dir` command line can override the configuration and reconfigure LuaRocks. * `site_config_*` is no more: LuaRocks is no longer dependent on a properly-written site_config file. Instead, it can *optionally* use `luarocks.core.hardcoded` for hardcoded values, or detect its configuration at runtime, based on OS detection, arg[-1] or command-line flags. * reduction of moving parts in the configuration: * `cfg.platforms` is no longer a globally-visible table; instead, `cfg` provides an API of read-only functions: `is_platform`, `each_platform`, `print_platforms`. * `cfg.*_proxy` options are no longer configured via the config files, but rather via the standard `*_proxy` environment variables. * `"windows"` is now the more general platform name of the Windows family. This is technically a breaking change but I don't expect it to cause problems with real-world rockspecs. * internal code reorganization in `luarocks.cmd` module | ||||
* | Tests: replace #blackbox with #integration and #whitebox with #unit | George Roman | 2018-06-04 | 1 | -1/+1 |
| | |||||
* | Reorganize test suite files | Hisham Muhammad | 2018-01-08 | 1 | -1/+1 |
| | |||||
* | Use versioned files only. (#734) | Hisham Muhammad | 2017-10-04 | 1 | -10/+2 |
| | | | | | | | | Let's take the opportunity of a new major version to make an important cleanup: getting rid of the error-prone unversioned configuration files. This drops support for: * Unversioned config.lua -> use config-5.x.lua * Unversioned luarocks/site_config.lua -> it always generates luarocks/core/site_config_5_x.lua * Unversioned lib/luarocks/rocks -> it always uses lib/luarocks/rocks-5.x | ||||
* | This doesn't produce an error, only a warning. | Hisham | 2016-10-29 | 1 | -1/+2 |
| | |||||
* | Fix of config test | roboo | 2016-08-22 | 1 | -19/+16 |
| | |||||
* | Fix of config test | roboo | 2016-08-22 | 1 | -22/+25 |
| | |||||
* | Windows and appveyor support for tests | roboo | 2016-08-21 | 1 | -19/+51 |
| | |||||
* | Remove some more unused stuff and globals from tests | Peter Melnichenko | 2016-07-08 | 1 | -1/+2 |
| | |||||
* | Make env vars, paths and run commands available on test env load | Peter Melnichenko | 2016-07-08 | 1 | -2/+2 |
| | |||||
* | Tests: disable insulation and use describe() instead of expose() | Peter Melnichenko | 2016-07-08 | 1 | -1/+1 |
| | |||||
* | Remove all the unused imports in test suite | Peter Melnichenko | 2016-07-08 | 1 | -2/+1 |
| | |||||
* | New test-suite for LuaRocks (#581) | robooo | 2016-07-07 | 1 | -0/+90 |
First version of new test-suite, using Busted framework based on Google Summer of Code project: https://summerofcode.withgoogle.com/projects/#5695811874717696 * Rewritten from Bash to Lua * Tests now check if they did what they were supposed to, beyond only checking success or failure of the `luarocks` command * Support for black-box (launching `luarocks` as an external command) and white-box (testing functions in modules directly) testing |