On Sat, Oct 16, 2010 at 5:58 AM, steve donovan <[email protected]> wrote: > On Fri, Oct 15, 2010 at 7:26 PM, Hisham <[email protected]> wrote: >> case, when using the distro-installed package, the user is not >> supposed to manage it with the language-specific manager anymore. > > Fair enough, can't have package managers fighting over ownership. > > For instance, I would like to make LuaGnome available to > Debian/Ubuntu/etc? users of LuaRocks, through the native > liblua5.1-gnome-0 package. So the task is to write a rockspec which > tells LR about the new modules and establishes a 'virtual' LR package. > Still thinking of the best strategy for this ... the idea is that I > could then package LuaGnome scripts and give LuaGnome as a LR > dependency. > > (the properties of a virtual package: it is _managed_ by the native > package manager and so LR will not mess with any of the .so files > already installed. The rockspec may have a payload looking like > 'aptitude install liblua5.1-gnome-0')
I believe the cleanest way to integrate distro-managed modules and luarocks-managed modules (if one would want to do such a thing; an idea I'm not really sold into) would be to just specify the distro-managed module in the external_dependencies section. -- Hisham _______________________________________________ Luarocks-developers mailing list [email protected] http://lists.luaforge.net/cgi-bin/mailman/listinfo/luarocks-developers
