On 7/16/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> A very vague thought: maybe what we need is a way to "talk" to other
> package managers, to have a bridge between our management/dependency
> system, and theirs. Perhaps implemented as a plugin-like system.
> Thinking out loud:
>
> If a dependency in the Dependencies file is named something like:
> RubyGems-rubyqt then it means it will be handled by the RubyGems
> plugin. The plugin script will respond to some minimal set of
> operations such as "is_installed", "install", "remove". Plugins would
> be written for those external managers. There wouldn't be recipes for
> each gem, or for each rock. A dependency like "LuaRocks-luasocket >=
> 2.0" would just call the LuaRocks plugin and the plugin would
> query/install LuaSocket using LuaRocks. We would need standard
> locations for these separate trees; I'm at a blank wrt this
> (/Files/LuaRocks/ would be the cowardly escape). A directory for ROX
> appdirs could fit into this scheme as well. Again, it is all still
> very vague in my head.
>
/System/Aliens/{RubyGems,LuaRocks,CPAN}? I think this is VERY
workable. Use upstreams packaging work but integrated into our dep
resolution.
--
Carlo J. Calica
_______________________________________________
gobolinux-devel mailing list
gobolinux-devel@lists.gobolinux.org
http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
