On Tue, Sep 18, 2012 at 06:37:20PM +0600, Ildar Mulyukov wrote: > > > %files > > > %lua_modulesdir/* > > > %lua_modulesdir_noarch/* > > > %luarocks_dbdir/%oname > > > %doc LICENSE NEW README docs_from_rockstree/* > > > %exclude %luarocks_dbdir/manifest > > > And we don't exclude manifest, we mangle manifest's name, and later > > reconstruct it in postinstall hook. So _patched_ luarocks can see > > rocks > > as preinstalled. > > My approach is different: > * any RPM with a rock excludes manifest because obviously it is the > shared manifest of all rocks installed in this tree > * installation/update/removal of an RPM which contains a rock > triggers the RPM filetrigger (the unique ALTLinux technology) which > regenerates the manifest. No postinstall scripts required. > > Hence it > 1. "just works" for rocks RPMs installed into one single rock tree and
And you "system" rocks invisible for luarocks, our approach make it visible. Also I believe you can hit a problem to build rocks with dependencies (luasec for example, without patching luasec pull own copy of loasocket into buildtree) ------------------------------------------------------------------------------ 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