From: Charles O Nutter <headius@...>
Date: 2006-06-15T04:52:47+09:00
Subject: Re: RubyGems for inclusion in JRuby

------=_Part_115826_11844311.1150314763676
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

At this point it's almost sounding like we should just leave our platform or
'arch' as 'java', and the default behavior for RubyGems would be to install
both sh and cmd scripts. This would cover not only cases where you're on one
platform or the other, but cases where we or someone else wants to ship a
single distributable that will work anywhere Java does.

The 'java' arch would then also preclude any platform-native libraries,
since we can't run them anyway. Those gem installs could come to a
screeching halt rather than fail later on.

Jim, would adding such rules for a 'java' arch fit well with how RubyGems
does such things?

On 6/14/06, Thomas E Enebo <enebo@acm.org> wrote:
>
> On Thu, 15 Jun 2006, Jim Weirich defenestrated me:
> > Charles O Nutter wrote:
> > > FYI, if platform was needed, we could most easily provide
> > > "java-windows",
> > > "java-x86", or "java-windows-x86" (or some combination) given what the
> > > JVM
> > > tells us (System properties os.arch = x86 and os.name = windows).
> > > Anything
> > > beyond that would require massaging "windows" and "x86" into something
> > > else.
> >
> > RubyGems uses platforms for two things[1].  The obvious use is selecting
> > the platform for possible gems to install[2].  The other use is when
> > installing command file, RubyGems will create .cmd files for all the
> > programs in the gem.  I would imagine that we still need to do this for
> > the JRuby version, right?  It seems to me we need to differentiate
> > between JRuby on windows vs JRuby on Unix.  Perhaps the platform string
> > is not the appropriate mechanizm for this.  I'm will to hear
> > alternatives.
>
>   I have not been following the thread as closely as I should have, so
> forgive me if this has been covered.  'java' is our platform for general
> Ruby behavior with the only exception of invocation scripts.  So host
> OS is a significant discrimator for external/installation scripts, but not
> for general Ruby capabilities of the interpreter at large (like regardless
> of host OS we do not support File.tty?).   It seems like this distinction
> may be a good option for gem creators.
>
> -Tom
>
> P.S. - I do things from cygwin on windows normally so I guess if I had
> a choice I would want a shell script in addition to a cmd file on
> Windows.  I am sure I am an oddity in that regard and I suspect this is
> up to the gem-maker.  I don't know if other have asked for this (and I
> know this has nothing to do with JRuby in particular).
>
> --
> + http://www.tc.umn.edu/~enebo +---- mailto:enebo@acm.org ----+
> | Thomas E Enebo, Protagonist  | "Luck favors the prepared    |
> |                              |  mind." -Louis Pasteur       |
>
>


-- 
Charles Oliver Nutter @ headius.blogspot.com
JRuby Developer @ jruby.sourceforge.net
Application Architect @ www.ventera.com

------=_Part_115826_11844311.1150314763676--