From: Florian Frank <flori@...>
Date: 2007-12-27T00:28:09+09:00
Subject: Re: Legacy support (Was: Base64 not there makes Rails 2.0.2 fail to load in 1.9.0)

Dirkjan Bussink wrote:
> You aren't the only one :).

I found it suspicious, too, that I should be the only one, that has ever 
tinkered with Mysql and Ruby 1.9. ;)

> Jeremy Kemper already wrote one too and submitted it to the MySQL
 > project on Rubyforge.

Oh, I didn't know, that the extension is now hosted there. I thought it 
was still at home here:

http://www.tmtm.org/en/mysql/ruby/

The google page rank of this URL is way higher, than the rubyforge URL.

I remember, that this used to be the case for the ruby-dbi library as 
well: for many years google would send you to the sourceforge project, 
where only older version were available. Before I figured this out, I 
thought dbi development had been discontinued. This could have been a 
bad sign for Perl programmers, that want to look into Ruby.

Maybe the homepage should be moved and redirect to 
http://mysql-ruby.rubyforge.org ? Or should the old homepage have link 
to the rubyforge project?

> It might be useful to somewhat structure the effort, so not everyone is 
> fixing the same stuff. A simple list with who's working on what and what 
> is already fixed, would be a huge improvement.

It's difficult to avoid that. I don't think, the changes will be that 
many, though. Adding some of the new 1.9 macros to the extension, if 
they aren't defined, makes them compile on both. In pure ruby libraries, 
the most work, I had to do so far, was to substitute sloppy 
Thread.critical hackery with higher order constructs.

-- 
Florian Frank