[Rubygems-developers] --destdir changed behavior again ?

[Jeremy Hinegardner]

On Sat, Nov 15, 2008 at 08:36:09AM -0300, Luis Lavena wrote:
> On Fri, Nov 14, 2008 at 8:55 PM, Jeremy Hinegardner
> <jeremy at hinegardner.org> wrote:
> > Hi all,
> >
> > I was packaging up rubygems 1.3.1 fo use at my work and it appears that the
> > setup.rb behavior has changed since 1.2.0.
> >

> 
> The change was introduced due a previous bug and the imposibility to
> rely on Pathname to resolve Windows paths.
> 
> Bundlign RubyGems with One-Click Installer generated issues, since by
> default it tried to perform all the destdir operations, even when you
> didn't used the parameter.
> 
> Back in July I introduced the change and asked more about this issue,
> since was making my life really hard to update since it's
> introduction.

Well it looks like i have those threads in my archive, but I failed to give them
due consideration, sorry about that.

> In any case, I was not pleased to break others implementations or
> process by this, but the feedback I got was somehow late in relation
> to my patch and the release process of RubyGems, so it became
> "official" at that time.

No worries, I've managed to work around it for now. 

> The references about this topic:
> 
> Request for comments:
> http://rubyforge.org/pipermail/rubygems-developers/2008-July/003969.html
> 
> Replies:
> http://rubyforge.org/pipermail/rubygems-developers/2008-August/004026.html
> 
> We use also destdir to package RubyGems separated from Ruby, but it
> was generating a complex folder structure (and errors due driver
> letters).
> 
> Anyhow, properly fix that benefit both of us will be really great. I
> tried to avoid any platform validations since thos are tend to be
> forgotten...

I'll submit a patch on rubyforge that may help.

enjoy,

-jeremy

-- 
========================================================================
 Jeremy Hinegardner                              jeremy at hinegardner.org