On Mon, Jan 19, 2004 at 01:35:31PM +0100, Michal Suchanek wrote: > > I have this problem: > -there are two usable versions of ruby in fink > -ruby 1.6.8 > -ruby 1.8.0 > -there is an application (freeride) that works with either version but > it needs two extensions to the interpreter > -fxruby > -ripper > The extensions are packaged for both versions of interpreter > ripper-ruby16, ripper-ruby18, fxruby-ruby16, fxruby-ruby18 > The interpreters have packages > ruby16, splitoff ruby 1.6.8, ruby18, splitoff ruby 1.8.0 > Each splitoff contains a link /sw/bin/ruby that points to ruby1.6 > or ruby1.8. So installing ruby-1.6.8-2 makes ruby1.6 the default > interpreter named just ruby.
This all sounds very standard so far. > Now the application needs that the default interpreter ruby has both > extensions. Do you really need the *default* interpretter to have both, or just "know a path to an interpretter that has both"? I.e.... > to show some possible configurations that do not work: > ruby16 + ruby18 + ruby 1.8.0 + ripper-ruby16 + fxruby-ruby18 + freeride > ruby16 + ruby18 + ruby 1.8.0 + ripper-ruby16 + fxruby-ruby16 + freeride why can't this latter one be made to work by explicitly calling ruby16 instead of just "default ruby"? > So I made ripper-ruby16 0.0.5-2 that has a splitoff ripper > 0.0.5-2-16, ripper-ruby18 with splitoff ripper 0.0.5-2-18, etc. > > Now there are two objections from the person who looked at it: > - dash in revision is illegal - can be simply replaced with something else > - these splitoffs do not look quite right > So i would like to know what is the right solution. What exactly is the purpose of these splitoffs and what do they contain? I.e., are you trying to emulate the ruby interpretter situation whereby one could isntall ripper for both ruby versions and then install one of their splitoffs that enables some /sw/bin program? Or are you trying to arrange so that other fink packages can use yours by simply "Depends: ripper" and be assured of a fully functional module *somewhere*? Based on the freeride example you give, you're in the same versioned-perl-module handbasket. If it's the freeride package (which is not ruby-versioned) that needs a certain suite of modules all in the "same ruby-version", it's up to that package to request them. Why can't it just pick a ruby and use it? dan -- Daniel Macks [EMAIL PROTECTED] http://www.netspace.org/~dmacks ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
