summaryrefslogtreecommitdiff
path: root/spec/fetch_spec.lua (follow)
Commit message (Collapse)AuthorAgeFilesLines
* tests: don't use validate-args rockspec in testsHisham Muhammad2022-03-061-1/+1
| | | | | | | | 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.
* tests: wait longer for mock server to startHisham Muhammad2022-02-171-1/+4
|
* fix: pack: rockspec with a bare file in the urlHisham Muhammad2021-03-221-2/+19
|
* editorconfig: trim trailing whitespaceHisham Muhammad2021-03-161-54/+54
|
* tests: shorter descriptionsHisham Muhammad2020-02-141-1/+1
|
* Tests: config: no need for special-casing WindowsHisham Muhammad2018-07-011-1/+0
|
* Tests: minor cleanupsHisham Muhammad2018-07-011-0/+1
|
* cfg, cmd: major reorganizationHisham Muhammad2018-07-011-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * `--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
* fs: make module loading side-effect free, require explicit init()Hisham Muhammad2018-07-011-0/+2
|
* Tests: replace small fixture files with inline contentGeorge Roman2018-06-211-13/+112
|
* Tests: fix fetch tests using the rockspecs moduleHisham Muhammad2018-06-141-66/+21
|
* Fix the collecting of coverage data from unit testsGeorge Roman2018-06-121-1/+2
|
* General refactor introducing Rockspec and Build.Opts objectsHisham Muhammad2018-06-061-9/+0
| | | | | | | | | | Adds a Rockspec object responsible for constructing all Rockspec tables in the manner of the Queries and Results objects, and a type-checked Build.Opts tables for build options, since the number of attributes passed around was getting out of hand. This allowed a major cleanup in the luarocks.build, luarocks.fetch and luarocks.cmd.write_rockspec modules.
* Tests: move is_basic_protocol to dirHisham Muhammad2018-06-061-11/+0
|
* Tests: collect coverage data from unit tests (#814)George Roman2018-06-051-0/+11
|
* Fix failing Appveyor testsGeorge Roman2018-06-041-1/+2
|
* Tests: replace #blackbox with #integration and #whitebox with #unitGeorge Roman2018-06-041-9/+8
|
* Improve the tests for the fetch moduleGeorge Roman2018-05-311-2/+356
|
* Add support for namespaces.Hisham Muhammad2018-04-111-3/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | For details of the new feature, see https://github.com/luarocks/luarocks/wiki/Namespaces This ended up being a huge commit because of some major refactoring motivated by the new feature: * new modules for some object types: * `luarocks.queries` - all functions that look for rocks in local or remote repositories now use objects constructed by this module: query objects contain the name, namespace and query constraints. Dependencies in a rockspec are also stored as query objects. * `luarocks.results` - all individual results produces from queries are returned in this format: result objects contain the name, namespace, version, arch and repo. * the `results` object was renamed to `result_tree`, to better reflect that it is not an array of `result` objects. * `luarocks.vers` was removed, its functionality was moved to better locations. Specifically on namespaces: * Commands that take a rock `name` can now take `namespace/name` (and alternately `--flags=namespace` so that URLs can be also installed with a nominal namespace). * Rocks installed from a namespace now create a `rock_namespace` file alongside `rock_manifest`, which is used when matching namespaced dependencies against locally-installed rocks. * Using namespaced dependencies in a rockspec, requires `rockspec_format = "3.0"`. * Tests under the `#namespaces` hashtag, all using a local repository.
* Tests: run our own local git-daemon repository for git testsHisham Muhammad2018-03-301-10/+23
|
* Reorganize test suite filesHisham Muhammad2018-01-081-1/+1
|
* Tests: fetching from git stores an identifierHisham Muhammad2018-01-021-0/+23
|
* Remove all the unused imports in test suitePeter Melnichenko2016-07-081-2/+1
|
* New test-suite for LuaRocks (#581)robooo2016-07-071-0/+16
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