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.


2011/9/13 Gerhard Lipp <[email protected]>:
> Hello Hisham,
>
> tango 0.2.1 (and 0.1.1) are ready; this time pointing to tags in github ;)
>
> https://github.com/lipp/tango/tree/0.2.1
>
> New features:
> - remote variable/state access
> - remote objects/classes (you name it)
>
> 0.2.1:
> tango-complete:
> https://raw.github.com/lipp/tango/0.2.1/rockspecs/tango-complete-0.2-1.rockspec
> tango-copas: 
> https://raw.github.com/lipp/tango/0.2.1/rockspecs/tango-copas-0.2-1.rockspec
>
> 0.1.1:
> tango-complete:
> https://raw.github.com/lipp/tango/0.1.1/rockspecs/tango-complete-0.1-2.rockspec
> tango-copas: 
> https://raw.github.com/lipp/tango/0.1.1/rockspecs/tango-copas-0.1-2.rockspec
>
> regards,
> gerhard
>

------------------------------------------------------------------------------
BlackBerry&reg; DevCon Americas, Oct. 18-20, San Francisco, CA
Learn about the latest advances in developing for the 
BlackBerry&reg; mobile platform with sessions, labs & more.
See new tools and technologies. Register for BlackBerry&reg; DevCon today!
http://p.sf.net/sfu/rim-devcon-copy1 
_______________________________________________
Luarocks-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/luarocks-developers

Reply via email to