On 27 May 2014 14:59, Tom N Harris <tellia...@whoopdedo.org> wrote:
> On Tuesday, May 27, 2014 11:46:19 AM Hisham wrote:
>> Those commands are essentially a frontend to `luarocks make_manifest`
>> + rsync so they don't do _that_ much, and I was basically afraid that
>> they would bitrot now that I won't be using them anymore. But no
>> problem, there's no hurry to rip them out of the codebase.
>
> Has anyone tried using make_manifest to maintain a rocks tree for satisfying
> dependencies provided by an external package manager? Usually, if I
> `apt-get install lua-markdown` that module won't be seen by LuaRocks. But I
> should be able to drop rockspecs for packages installed by apt and build a
> manifest that describes these packages. LuaRocks can then query this tree to
> find dependencies. But I don't want LR to try to install or remove anything
> from that tree.

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!).

-- Hisham

------------------------------------------------------------------------------
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

Reply via email to