A mirror of https://github.com/luarocks/luarocks.git https://git.lua4.win/luarocks/atom?h=fix-lua-link-windows 2022-04-17T00:17:34+00:00 2022-04-17T00:17:34+00:00 Hisham Muhammad hisham@gobolinux.org 2022-04-16T21:53:07+00:00 urn:sha1:0f82063a51cd9197edd214e0427fe4e84ae9c0b9 2022-03-07T02:04:20+00:00 Hisham Muhammad hisham@gobolinux.org 2022-03-06T17:52:15+00:00 urn:sha1:8de1500a25d1e43cd6ed26b4d93f956651b53b6a 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. 2019-11-29T21:36:42+00:00 Hisham Muhammad hisham@gobolinux.org 2019-11-08T21:19:17+00:00 urn:sha1:acf8bcb82ae697a5bac94bfbe93c3ad9d7487795 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. 2018-07-31T18:50:22+00:00 George Roman george.roman.99@gmail.com 2018-07-27T19:29:11+00:00 urn:sha1:c02b5989301312dfee02c195497e119bd0c73b85 2018-05-07T22:27:37+00:00 Hisham Muhammad hisham@gobolinux.org 2018-05-07T14:22:07+00:00 urn:sha1:1dcdaa77c0a52ad02f49bc7fdde2fd7dee956ddf 2018-04-13T20:11:12+00:00 Hisham Muhammad hisham@gobolinux.org 2018-04-12T20:13:43+00:00 urn:sha1:2871199838131b5a4c5a99d8e1fedbcd26017b0e 2018-04-11T17:38:06+00:00 Hisham Muhammad hisham@gobolinux.org 2018-04-05T18:50:45+00:00 urn:sha1:835d21e98e95e0ed2b6b028ddb06fe87427e5488 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. 2018-04-11T17:38:06+00:00 Hisham Muhammad hisham@gobolinux.org 2018-04-02T16:12:17+00:00 urn:sha1:fa3f92059c51cbcdf26df9a010f5eadd11a9567d