On Tue, Sep 13, 2011 at 10:45 AM, Gerhard Lipp <[email protected]> wrote: > Sorry for that! > Perhaps the versions should just be named: > tango 0.2 and tango 0.1 > > I tested install with: > luarocks install > https://raw.github.com/lipp/tango/0.2.1/rockspecs/tango-copas-0.2-1.rockspec > > 0.x is meant to describe a certain set of features whereas 0.x.y > refers to some kind of fix with same features as 0.x. > As I would prefer to refer to an unmodifiable tags of the repo, I > would end up releasing e.g.: > "variant a" > tango-0.2-1.rockspec > tango-0.2.1-1.rockspec > tango-0.2.2-1.rockspec > tango-0.2.3-1.rockspec > > "variant b" > Instead - if a release is worth updating the rock repo - i'd like to release: > tango-0.2-1.rockspec (referring some tag 0.2.1) > tango-0.2-2.rockspec (referring tag 0.2.3) > tango-0.2-3.rockspec (referring tag 0.2.7) > > Is this compatible with your luarocks versioning? > If not, I can stick to varient a.
Variant "a", certainly. The "-x" refers to the rockspec only, so, for example, all 0.2-x should point to the same github tag. If they are different upstream sources, they should be 0.2-1, 0.2.1-1, 0.2.2-1 and so on. Note that when I noticed the problem with the branch="master" in the rockspec, I had already fixed that an uploaded a 0.1-2 to the repository with the corrected tag (that was before you asked me to wait...). "-x" are just rockspec revisions. -- -- Hisham http://hisham.hm/ - http://colorbleed.com.br/ ------------------------------------------------------------------------------ BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA Learn about the latest advances in developing for the BlackBerry® mobile platform with sessions, labs & more. See new tools and technologies. Register for BlackBerry® DevCon today! http://p.sf.net/sfu/rim-devcon-copy1 _______________________________________________ Luarocks-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/luarocks-developers
