On Sun, Mar 27, 2011 at 12:28 PM, Hisham <[email protected]> wrote: > On Fri, Mar 25, 2011 at 3:15 PM, Peter Drahoš <[email protected]> wrote: >> - Reconsider removing support for "rockspec" installation, instead use >> "rock" only packages, the former causes fragmentation and download problems. > > Using bare rockspecs is popular among developers (myself included). > LuaRocks already favors rock files over rockspecs in installation, > which covers download problems for repositories we keep (nowadays I > consistently upload .src.rock files along with the rockspecs).
I think the following observations illustrate why LuaDist doesn't use rockspecs nor GNU patch. I was looking today at the SCM rockspecs [1], and one thing I think may be missing is that these don't specify the particular snapshot(s) in which the rockspec was authored against. So, how do I know whether the rockspec is up-to-date? and if it is not up-to-date, how do I know which changesets must be examined to properly update the rockspec? That is one thing explicit in LuaDist by way of git. As has been mentioned, LuaDist only deploys via something analogous to LuaRocks "rocks". The sources of the rocks for a package are maintained in a git repo. The upstream sources these were derived from are also maintained in a separate branch in git (via fork or bridge). These two branches share common ancestors, explicitly known by git, so continually merging new commits from the upstream into the downstream source rock is a systematic process. [2] You can think of a source rock as a snapshot in the downstream that branches off of a particular snapshot of the upstream. The diff between these two snapshots (typically consisting of metadata and code changes) is essentially what the rockspec is in LuaRocks, but the concept is implicit in git and can be reconstructed from git if need be by developers--most end users just need the rock. In other words, git replaces the function of separate rockspecs in LuaDist. [1] http://luarocks.org/repositories/rocks-cvs/ [2] https://github.com/LuaDist/vstruct/network [3] http://lists.luaforge.net/pipermail/luarocks-developers/2009-November/001299.html _______________________________________________ Luarocks-developers mailing list [email protected] http://lists.luaforge.net/cgi-bin/mailman/listinfo/luarocks-developers
