luarocks/configure, branch 2.4.3 A mirror of https://github.com/luarocks/luarocks.git https://git.lua4.win/luarocks/atom?h=2.4.3 2017-04-14T18:26:19+00:00 Fixed wrong "interp" in the configure file 2017-04-14T18:26:19+00:00 Evgeny Shulgin izarizar@mail.ru 2017-04-14T18:26:19+00:00 urn:sha1:3dcfa00db4b29609d83f356502ef83c5eefe2a34 Fixed wrong "interp" instead of "where" in the configure file Prefer versioned Lua interpreter if it exists. 2016-10-28T13:53:07+00:00 Hisham hisham@gobolinux.org 2016-10-28T13:53:07+00:00 urn:sha1:66cc4dfe45b4691a83b1b234bb626b60c16fd020 This avoids in practice a problem that occurs in this scenario: 1. user installs Lua 5.1, gets lua and lua5.1 binaries 2. user installs LuaRocks, it detects and uses lua 3. user installs Lua 5.2, gets lua and lua5.2 binaries (lua is replaced) 4. user installs LuaRocks with --lua-version=5.2, it detects and uses lua 5. luarocks-5.1 now uses lua, which is Lua 5.2, rockspecs get passed the wrong value of $(LUA) Check if header matches interpreter. 2016-10-26T17:19:42+00:00 Hisham hisham@gobolinux.org 2016-10-26T17:19:42+00:00 urn:sha1:86e1bef85084b5bf09688bd19077a8eaa82ae15c Improve check of Lua interpreter 2016-10-26T17:18:58+00:00 Hisham hisham@gobolinux.org 2016-10-26T17:18:58+00:00 urn:sha1:48e5329617f20e97262ca5510264fdb5d645ae6f (e.g. allow it to find `lua5.1` when lua is 5.3 and only `--lua-version=5.1` is given). Relax Lua version detection to support Ravi 2016-10-14T20:53:34+00:00 Peter Melnichenko mpeterval@gmail.com 2016-10-14T20:45:15+00:00 urn:sha1:23043499b9a5423ecbc19e968142df17dc5d15d1 Ravi has "Ravi 5.3" as _VERSION. Don't use _VERSION:sub(5) to get Lua version, match " (5%.[123])$" instead. Test that 'unzip' is present in the $PATH. 2016-02-29T21:48:37+00:00 Hisham hisham@gobolinux.org 2016-02-29T21:48:37+00:00 urn:sha1:84b1b88895f091c3a6c90dc921038c9294e43e36 Fix find_program() in configure 2015-12-06T18:57:32+00:00 mpeterv mpeterval@gmail.com 2015-12-06T18:53:59+00:00 urn:sha1:515db853f6631e92b5950bcedf392db2d35e919a which returns path to the program, not to the directory containing it. That causes errors when configuring without --with-lua. The fix is to apply 'dirname' if 'command -v' was a success. Use `command -v` for obtaining executable path. 2015-11-08T03:02:08+00:00 Ruslan Kiianchuk ruslan.kiianchuk@gmail.com 2015-11-08T03:02:08+00:00 urn:sha1:62017cc5a39a0298a3227ebb6182fd83f28b5e22 Seems like `command -v` is defined by POSIX and therefore should be compatible with all POSIX OSes. Fix `find_program` function to be less fragile 2015-11-07T22:28:26+00:00 Ruslan Kiianchuk ruslan.kiianchuk@gmail.com 2015-11-07T22:28:26+00:00 urn:sha1:6f70ad579fef9eef027991dae6b1d4fc62510588 Look for executable path using system utility `which` instead of fragile regular expressions. See $447 for details. Also see discussion in [neovim](https://github.com/neovim/neovim/issues/3620#issuecomment-154757577) issues. Fix documentation of --lua-version 2015-09-17T19:46:25+00:00 Hisham Muhammad hisham@gobolinux.org 2015-09-17T19:46:25+00:00 urn:sha1:0d2053ea208a5326240331bf44eab52976076c32