Re: [ANN] 'xtable' module updated to 5.3, 64-bit

[Hisham <h@...>]

On 8 September 2015 at 14:56, Dirk Laurie <dirk.laurie@gmail.com> wrote:
> 2015-09-08 17:16 GMT+02:00 Hisham <h@hisham.hm>:
>
>> That is not how version numbers roll in LuaRocks (and in any other
>> package management system). If there are any changes in the upstream
>> code, it _is_ a new version.
>>
>> If you're saying this in the sense that "the program version for Lua
>> 5.1.1 and 5.1.5 are both 5.1", it's not the case either: first,
>> because from a package manager perspective 5.1.1 and 5.1.5 _are_
>> different versions; second, because you even list a function that has
>> been renamed since xtable 1.0.2. Therefore, there are definitely
>> incompatible changes.
>>
>> In short: version number equality means code identity. The revision
>> number suffix is for versioning the rockspec itself.
>
> Well, let's wait to see if there are ever any other versions,
> or any other users except me.

It is less likely for it to have users if you don't version your
releases and publish them. :) If a package is not on luarocks.org
people can't refer to it as a dependency in their own rocks.

Note that if you decide to upload a release to luarocks.org, whatever
the version number, its URL should not point to the Github master.zip,
as this is a moving target. The procedure is to either make a tag and
point to the zip of the versioned tag, or, preferrably, use git:// in
the source.url field and a tag in the source.tag field. Use the
`luarocks upload <rockspec>` command to make sure a .src.rock file is
included.

-- Hisham