A mirror of https://github.com/luarocks/luarocks.git https://git.lua4.win/luarocks/atom?h=test-pin 2024-02-29T15:46:16+00:00 2024-02-29T15:46:16+00:00 Hisham Muhammad hisham@gobolinux.org 2024-02-29T03:46:06+00:00 urn:sha1:f76b7a2b13e411df2e696146bb0a6396781acd92 2024-02-27T16:28:33+00:00 Hisham Muhammad hisham@gobolinux.org 2024-02-26T21:30:31+00:00 urn:sha1:03e401231972d7b4db0145a71ce74d5d18d1a901 2021-03-16T19:32:45+00:00 Hisham Muhammad hisham@gobolinux.org 2021-03-16T16:36:26+00:00 urn:sha1:8f3ce333e7a1abfc6bf0488817d9eff4a2fd443f 2020-02-14T12:53:12+00:00 Hisham Muhammad hisham@gobolinux.org 2020-02-14T12:53:12+00:00 urn:sha1:bd27d052eaf856bf24c77f556a50b7e19f11cba1 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-06-04T18:41:51+00:00 George Roman george.roman.99@gmail.com 2018-05-31T21:05:49+00:00 urn:sha1:4e8c650d7daac769f9af843b1578dd2521318972 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-01-08T18:26:48+00:00 Hisham Muhammad hisham@gobolinux.org 2018-01-08T18:26:48+00:00 urn:sha1:d80124af9cd929b395b4d4c353b51ccc902a3f9e 2017-10-04T14:14:42+00:00 Hisham Muhammad hisham@gobolinux.org 2017-10-04T14:14:42+00:00 urn:sha1:84b4fe99cac37850a97858e0b641043bd3178d8a 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