Re: Looking for rockers...

[Hisham <h@...>]

On 13 October 2013 06:50, Marc Balmer <marc@msys.ch> wrote:
> Am 13.10.13 10:36, schrieb Marc Balmer:
>> Am 12.10.13 18:53, schrieb Hisham:
>>
>> [...]
>>
>>> I took a stab at writing rockspecs for these!
>>>
>>> http://luarocks.org/repositories/rocks-scm/luaproxy-scm-1.rockspec
>>> http://luarocks.org/repositories/rocks-scm/luafcgi-scm-1.rockspec
>>> http://luarocks.org/repositories/rocks-scm/luapgsql-scm-1.rockspec
>>
>> Many thanks for your effort!
>>
>>> We have a problem with luajson: the name is already taken.
>>
>> That was to be expected, given that there are many modules for JSON.
>> Can you tag such packets with a secondary value besides the name?  e.g.
>> the name of the author or so?
>>
>>> Note that these are "scm" rockspecs: they point to the latest sources
>>> in your SCM (source control manager), i.e., your git master HEAD. So,
>>> they are not on the main repository (
>>> http://luarocks.org/repositories/rocks ). Please tag version numbers
>>> in your repo (something like `git tag v0.1` is fine), and I'll make
>>> versioned rockspecs and upload the to the main repository (these have
>>> the advantage of not being "moving targets", so the repository keeps a
>>> copy of the sources, and other rockspecs may specify it as
>>> dependencies).
>>
>> Ok, I will look into how I have to do that with git.  I also have
>> updates for all modules (to make them work with 5.1 _and_ 5.2).
>
> The modules are updated and tagged on github.com now.

Cool! But it looks like they're not tagged in github (you can verify
that by clicking on the "branch: master" button and then "tags" in the
web UI). You need to run `git push --tags` for the tags to upload.

-- Hisham