On 10/22/07, Eric Hodel <[EMAIL PROTECTED]> wrote:
> On Oct 22, 2007, at 12:26 , Luis Lavena wrote:
> > I'm checking some odd naming behavior with latest beta.
> >
> > I just installed a gem with platform mswin32, which installed just
> > fine, but found that it's named wrong by RubyGems.
> >
> > as Example:
> >
> > mongrel-1.0.1-mswin32.gem, install just fine, it list just fine.
> >
> > Folder on which is installed:
> >
> > mongrel-1.0.1-mswin32, everything seems ok.
> >
> > [...]
> > {:path=>"mongrel-1.0.2-x86-mswin32-60", :gem_name=>"mongrel"},
> > [...]
> >
> > please note that the platform for mongrel isn't mswin32, but
> > x86-mswin32-60 ... and don't match with the folder it installed...
> >
> > gem#name is returning that, disregarding the current folder where the
> > gem was installed...
>
> I tried to force converting all legacy platforms, but found it was
> too difficult due to the way that platforms are loaded. RubyGems is
> smart enough to correctly uninstall a legacy platform gem. You can
> access the legacy gem via Gem::Specification#original_platform.
>
> I think this is ok, since Gem::Installer and Gem::Uninstaller take
> care of the details for you.
>
Since GemPlugin (the one used by Mongrel) rely on RubyGems to find and
load the additional gems, we should fix this (I mean, gem_plugin, not
rubygems).
I'll check what can we do so avoid conflict when updated rubygems get released.
--
Luis Lavena
Multimedia systems
-
Leaders are made, they are not born. They are made by hard effort,
which is the price which all of us must pay to achieve any goal that
is worthwhile.
Vince Lombardi
_______________________________________________
Rubygems-developers mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/rubygems-developers
