On Tuesday, May 27, 2014 05:16:10 PM Hisham wrote: > The effort is to maintain a file mapping the names used by your pkg > manager for modules to rock names. Once that mapping is in place > generating the manifest would be the easy part. The mapping is the > hard part because it's different for each distro and therefore outside > of the scope of rock authors (and LuaRocks maintainers!).
It would be the job of the packager to supply a copy of the rockspec. This is the only sane way because a distributor may have modified the software so it doesn't match any rockspec version on MoonRocks. I just tried it but ran into what I think is a bug in make_manifest. When reading the "rock_manifest" that corresponds to a rockspec, it looks in the configured paths which may not be the tree that was passed as the argument. -- tom <tellia...@whoopdedo.org> ------------------------------------------------------------------------------ The best possible search technologies are now affordable for all companies. Download your FREE open source Enterprise Search Engine today! Our experts will assist you in its installation for $59/mo, no commitment. Test it for FREE on our Cloud platform anytime! http://pubads.g.doubleclick.net/gampad/clk?id=145328191&iu=/4140/ostg.clktrk _______________________________________________ Luarocks-developers mailing list Luarocks-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/luarocks-developers
