On 7/17/07, Michael Homer <[EMAIL PROTECTED]> wrote: > On 7/17/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. > That works for me. I like it a lot, in fact. It's flexible and it's
Yeah, I feel quite good about it too (and I loved Carlo's suggestion of /System/Aliens/ :) ). > integrated with the rest of the system. Would it create /Programs > directories for each one? I'm assuming no, since `gem install ...` > could install more than one gem, and catching that would be hard. No, it wouldn't. > It wouldn't make Freshen's life too hard either. It would mean that it > couldn't do a full system update, unless there were some way to get a > list of all installed and available gems/rocks/modules (which I think > might be a bit of a stretch). I think that's probably an acceptable > trade-off. Obtaining a list of all installed modules doesn't sound hard, I think all managers provide a direct way to get this, but a list of available versions may be more problematic, and the interactions between the two worlds could be hard to work out. If Freshen limits itself to keep the /Programs tree updated and talk to the alien dependency system to make sure that they're providing any alien depenencies required by programs in /Programs, that would already be great. -- Hisham _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
