Open wsfulton opened 9 years ago
That would be great. But I think that is outside of the scope of this project.
This project (lua-appveyor-example) builds a matrix, so each commit would be tested with Lua versions 5.1 to 5.3. Versions 5.2 and 5.3 are additionally built with compatibility flags disabled. Each variant is built in 32 and 64 bits. And soon, each of those variants will be built using different versions of Visual Studio and MinGW. I don't know how Chocolatey could accomodate all those Lua versions.
Nevertheless, I'd love to be able to just cinst lua5.3
and be on my way.
I havn't ever set up a chocolatey package so don't have the experience of packaging something up for Chocolatey, but I too would like to simply use Chocolatey to obtain Lua. Your build script is probably half way there for setting up a Chocolatey package as it looks like you've got scripts to build Lua on Windows.
I don't have experience with Chocolatey packaging. The scripts I'm using to build Lua are the work of @Tieske (https://github.com/Tieske/luawinmake).
Wouldn't it make more sense to make Lua available on Chocolatey and then use Appveyor's support to download the appropriate version? Then Lua wouldn't need compiling as the binaries would be downloaded from Chocolatey and would be a far more collaborative and efficient approach.
https://chocolatey.org/packages/lua.