|
On Sep 8, 2015 8:36 AM, "Dirk Laurie" <dirk.laurie@gmail.com> wrote:
>
> 2015-09-05 22:34 GMT+02:00 Hisham <h@hisham.hm>:
>
> > A suggestion: make Git tags for your releases, as in
> > git tag v1.0.2
> > git push --tags
> >
> > So you can specify them in rockspecs for a given version:
> >
> > source = {
> > url = "" href="http://github.com/dlaurie/xtable">github.com/dlaurie/xtable",
> > tag = "v1.0.2",
> > }
> >
> > When uploading to the luarocks.org server using
> > luarocks upload xtable-1.0.2-1.rockspec
> > it will generate a .src.rock file containing the code for that
> > specific tag (the end user does not need to have git installed). You
> > could use a download URL for your .zip file, but having Git tags for
> > releases is a good idea as it lets users browse the code for specific
> > releases online on Github more easily.
>
> I'm not yet ready for either uploading to the server or
> making a tag but anybody wishing to test out the current
> version can install it using Luarocks on the attached rockspec
> (almost identical to the one Philipp provided).
>
> Main differences between 1.0.2 and 1.0-4:
>
> 1. Note the hyphen: LuaRocks naming convention in effect.
This should be 1.0.4-1 (that is, if you're skipping 1.0.3). "1.0.4" is the program version, and the "-1" suffix is the rockspec revision. The idea is that you increment the revision if you submit a fixed rockspec that points to the same code.
> 2. Works under Lua 5.1, 5.2 or 5.3. LuaJIT not tested, does
> LuaRocks support it?
> 3. 'block.move' renamed to 'block.copy' since there now is
> 'table.move'.
> 4. The description of "trisect" has been rewritten.