[Lua] Windows install instructions for Lua / Busted for this track do not work
- Dominant language
- No language data
- Stars
- 3
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
https://exercism.io/tracks/lua/installation
This does not work on a fresh Windows 10 system, and although I went through a lot of attempts at workarounds I eventually had to give up on getting Lua, LuaRocks, or Busted working natively. But along the way I discovered a whole cascade of issues:
* `choco install lua` installs a version of LuaRocks that is incapable of completing the next step, throws error: `Error: Parse error processing dependency 'lua_cliargs = 3.0`
* `luarocks install busted` fails, because the wrong LuaRocks version is incapable of processing the dependecies for Busted.
* If you force Chocolatey to install the correct version of LuaRocks, using `choco install luarocks`, `luarocks install busted` still fails for not one, but two reasons:
- The "wrong" LuaRocks version is still installed by the previous `choco install lua` installation, and overrides the newer LuaRocks install from working
- There is no compiler available by default on Windows, so even if you fix the above LuaRocks issue, still no joy.
- If you remove the first `choco install lua` installation in favor of the LuaRocks one, Lua is no longer on the path either...
* If you navigate that minefield somehow, you get to the point of installing Visual Studio, which requires knowing what components to install and also is a giant multi-GB install, you do get a compiler
* Most people won't realize that in order for LuaRocks to find this compiler, you have to run LuaRocks from the magical **"Visual Studio 2019 Developer Command Prompt"** installed by the Visual Studio tools, not just any command prompt
* At this point, LuaRocks will succeed at installing, and building, Busted. However, neither Lua nor Busted is available from any command prompt, any user needing the help of the install instructions stands no chance to find out where these are installed or how to add them to the system Path. And frankly, neither could I, despite not being a novice.
My workarounds were:
* Installing Lua by just downloading a simple precompiled Lua binary (e.g. [from LuaBinaries](https://sourceforge.net/projects/luabinaries/files/5.3.5/Tools%20Executables/)), adding it to the Path manually
* Getting Busted working by, yes seriously, installing Ubuntu WSL from the Microsoft Store, installing Lua & LuaRocks / installing Busted using LuaRocks / funally running Busted *from* Ubuntu WSL, against the Exercism exercise path. Fortunately this can be easily done from any terminal (including cmd or Git-bash from within VS Code) on the current directory by just typing `wsl busted`, but it's still a massive hack.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.