Published rockspecs are not version-locked

[leso-kn]

Hi there! :)

First of all, thank you for creating luachild! I maintain a few projects based on it.

One of them is packaged for Alpine Linux and we just discovered that the recent merge of #5 causes the downstream build to fail (see gitlab.alpinelinux.org/alpine/aports!102882).

This should not happen since the Alpine package uses luachild ~> 0.1 specifically, so changes to the master branch should not affect it.

Looking at https://luarocks.org/manifests/pocomane/luachild-0.1-2.rockspec, I discovered that source.tag is missing.

This means that luachild v0.1 will actually use the master branch instead of the v0.1 tag.

[leso-kn]

Since there were some recent merges:

• Fix missing headers for LuaJIT #5
• Add Lua 5.1 support #6

and some more are pending:

• Environment variables may start with = #7
• Doesn't work with lua51 #8

I would suggest to address this by creating a new version and including source.tag = 'v0.2'.

If desired, there could also be a revision of v0.1 which adds the missing option.

---

Since pull-requests do not work on git tags such as v0.1:

See leso-kn/luachild:rockspec-v0.1-add-source-tag.

[leso-kn]

PS: In case you would like some assistance with maintaining the repository @sewbacca or I would offer ourselves as collaborators :)

See my previous comment on #5.