On 7/17/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Michael wrote: > > Isaac wrote: > > > The naming scheme... "RubyGems-rubyqt" would look like any other program > > > name, should there be some more distinctive punctuation like > > > "RubyGems:rubyqt" (... _is_ that more distinctive?)? Also I think we > > > will have to provide partial dependency files when a system package is > > > required (e.g. I'm assuming rubyqt requires some version of Qt to be > > > installed), since the ruby "gems" system can't know what we call our > > > _packages_ even if it knows it requires a file like /usr/include/qt.h > > > (or a .so file, etc.). > > That's a very good question. > > Yeah, you brought a very important point. > > > How is that going to work? Catching it > > for "gem install rubyqt" probably won't be possible, but something > > depending on RubyGems:rubyqt (I like that syntax, too) shouldn't fail > > to compile. We could just list Qt in the dependencies of everything > > requiring the Ruby bindings, but that's a little messy and seems like > > unnecessary duplication. > > > > It would also introduce the need to order dependencies for non-meta > > recipes which I don't like so much from the perspective of trying to > > resolve a valid order amongst many programs. [Explanatory sidebar: I > > don't want to have to make Freshen order things as they're listed in > > the recipe Dependencies, because most of the time it doesn't matter > > and is arbitrary (alphabetical). If order matters, resolving among > > multiple programs becomes impossible when one orders Qt before another > > package and another puts it after, creating a loop. There's no real > > way to decide which one should be followed.] > > > > Maybe a compatibility layer? A file of the format "RubyGems:rubyqt Qt > > >=3.0, <=4.0" that will make Compile do the right thing? I don't > > really like that solution, since we can't possibly keep up with every > > package in every packaging system. > > Sounds like an acceptable compromise. We can't keep up with every > package in every packaging system, but we could keep up with the alien > packages that are referenced in GoboLinux recipes. > And that is really what we need.
> If the user installs rubyqt from the command-line using gem directly, > then well, hopefully he'll get a good error message telling them to > "install qt" and they'll be able to install it using the facilities > provided by the system, as it would happen on any other distro. > That is a great base level experience. Most failures (especially the common stuff) have REALLY good error messages saying what you need to install. This level of utility is so high, it doesn't depend on the above enhancement to Compile. -- Carlo J. Calica _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
