On Mon, Sep 17, 2012 at 04:26:11PM -0300, Hisham wrote: > > I develop tool to generate proper debian/ and build few "packaged" rock > > for ubuntu/natty. Patch to LR (discussed in this thread) -- part of > > this work. It required to allow rocks installed in old fashion way use > > "system-wide" installed packages. Built packages have little manifest, > > inside /usr/lib/pk-rocks-tree/lib/luarocks/manifest.d/$package > > Full manifest rebuilt in /usr/lib/pk-rocks-tree/lib/luarocks/manifest.d > > on any install/remove operation. Little "runtime support" care about it. > > What does /usr/lib/pk-rocks-tree/lib/luarocks/manifest.d/$package > contain? Isn't that functionally equivalent to > .../lib/luarocks/rocks/$package/$version/rock_manifest ? >
literally -- contain manifest for single rock. Later they merged by utils.deep_merge from LR code. I know -- we can reconstruct manifest from .../lib/luarocks/rocks/$package/$version/rock_manifest + rockspec, but I prefer easy way: rock built with luarocks make --tree=.../debian/tmp/usr/lib/pk-rock-tree and later: mv ../lib/luarocks/manifest ../lib/luarocks/manifest.d/$package (i believe manifest don't contain any path, but if any -- it should be corrected on this step) PS I know -- this solution is not ideal, but it works for me. ------------------------------------------------------------------------------ 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 Luarocks-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/luarocks-developers
