Hisham, I've been tinkering with rock support in our build system but I'm running up against the issue of having dependencies installed regardless of whether I start from source (build) or an existing rock that I've made (pack). I note that the packed binary rock has files laid out differently that the installed rock, which I understand. However, what I think I want is "--deps-mode=none" such that I can do a self-contained install to a temporary tree (my proto area) and have that only contain the rock that I explicitly built, not any of its deps. I will then repeat the process for all of the deps declared in the original rock's manifest, and make those native package dependencies of the first rock's native package.
By way of example, the rock I'm testing with is "busted". What I think I want to do is be able to: luarocks --tree=/path/to/my/proto --deps-mode=none build busted and have /path/to/my/proto contain only the "busted" rock, which I will then turn into a native package whose deps (penlight, say, luafilesystem, etc.) are other native packages containing single rocks, built the same way. When installed, the tree would look the same as if I had done the build with all the deps. I believe I can mechanize the discovery of these deps in my build system, via the source rockspec. That brings up another question though-- do rocks distinguish between dependencies for build-time vs. run-time? If not, I will assume all dependencies are both. Thanks, Eric ------------------------------------------------------------------------------ _______________________________________________ Luarocks-developers mailing list Luarocks-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/luarocks-developers
