Hello,
Please bear with me if all this seem straightforward to you, but I am
no Git guru :-)
Currently Lanes builds against Lua 5.1.
Time has come to create a version compatible with Lua 5.2.
Lanes is hosted at GitHub. My idea would be to take the master branch,
and create a 5.1 branch. Then the master branch can continue to evolve
to become 5.2-compatible.
However, there are probably people that will continue to use Lanes
with Lua 5.1 (or LuaJIT2).
They should still be able to install an appropriate rockspec.
The current rockspec reads:
source= {
url= "git://github.com/LuaLanes/lanes.git",
branch= "v3.1.1"
}
Where v3.1.1 is in fact a tag.
Now let's say I do some changes to the "master" branch for Lua 5.2
compatibility, and bump the version to 3.2.0. I'll then want to create
a tag "v3.2.0".
Then I'll do a fix in the 5.1 branch, bump version to 3.1.2, and I'll
need a tag "v3.1.2".
How to I say to Git that tag "v3.2.0" applies only to the "master"
branch, and that tag "v3.1.2" applies only to the "5.1" branch?
I have read what info I could fond about Git and tags, but didn't find
any satisfactory answer.
Should the respective rockspecs read:
source= {
url= "git://github.com/LuaLanes/lanes.git",
branch= "master",
tag= "v3.2.0"
}
source= {
url= "git://github.com/LuaLanes/lanes.git",
branch= "5.1",
tag= "v3.1.1"
}
?
Thanks in advance for any insight on the bast way to handle this.
--
Benoit.
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Luarocks-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/luarocks-developers
