Re: Tempfile#unlink changes in Ruby 1.9.1-p152

[Ryan Long <ryan@rtlong.com>]

Niels,

I just wanted to add: after reading that I decided to grab the latest
stable ruby from svn. I'm way over my head with this stuff, but after
successfully installing ruby and attempting to use Passenger, it
continued to fail with this same error. I also cloned the bleeding-
edge rack overwriting my rack gem (I didn't know if that would work or
not, but I know rack is a dependency of Rails so I did'nt know how
else to do it...) with no luck. I did have some trouble with that
version of Ruby and sqlite3-ruby, so I've reverted back to 1.9.1-p243

Ryan

On Jul 18, 6:43 pm, Niels Ganser <ni...@herimedia.com> wrote:
> Eric,
>
> 2009/7/19 Eric Wong <normalper...@yhbt.net>
>
>
>
> > Thanks for the heads up, I just posted my thoughts on Redmine about this.
> > Hopefully the Ruby team is willing to fix it.
>
> Thanks for putting this to their attention.
>
> I've updated the issue with links to the original discussion on
> ruby-core in 2004. Both the its author and matz decided the patch, as
> recently introduced, wouldn't be a good idea:http://blade.nagaokaut.ac.jp/cgi-bin/vframe.rb/ruby/ruby-core/2848?26....
>
> > If we have to go this route, what about just explicitly unlinking it?
> > I'm not going to go as far as undefining the finalizer that Tempfile
> > defines since the finalizer checks if the file exists before unlinking
> > anyways.
>
> I don't think any change in the rack codebase will be necessary as I
> fully expect this to be fixed in Ruby before the next release.
> Considering that many people are even still using 1.8 I don't think
> too many compile from trunk or any other svn branch for that matter.
> Those who do would probably check the list here when in trouble, no?
>
> Cheers,
> Niels