Re: Bug#538660: ITP: ruby1.9.1 -- Interpreter of object-oriented scripting language Ruby 1.9.1
On 26/07/09 at 12:52 +0200, Michael Banck wrote:
> On Sun, Jul 26, 2009 at 05:06:02PM +0900, akira yamada wrote:
> > (We have already ruby1.9 package. But this package is needed for
> > transition to Ruby 1.9.1 from Ruby 1.9.0. Please refer to debian-ruby
> > list if you have questions.)
> I don't know; maybe you should explain while you need a transition for a
> micro-release update. Is ruby the new haskell?
You forgot to Cc debian-ruby@, as explicitely asked in the ITP.
Ruby upstream has some issues (and I'm not even talking about Rubygems).
Ruby 1.9.1 is not a micro-release. It's the current stable branch of
ruby, with 1.9.1-p0 first released in december 2008, then micro-releases
(-p129 and -p243) released on 12/05 and 18/07. 1.9.2 is planned to be
released in december 2009.
Our problem is that 1.9.1 broke API/ABI (no big changes, though, AFAIK)
compared to 1.9.0, and expects ruby libraries to be installed in
/usr/lib/ruby/1.9.1 instead of /usr/lib/ruby/1.9.0. So ruby libraries
needs to be transitioned anyway. (It is currently expected 1.9.2 to NOT
break ABI/API, on the other hand).
Keeping the ruby1.9 source+binary would have meant breaking users'
systems on upgrade (or blocking the upgrade until all libs have been
transitioned using Breaks: fields). We don't expect the transition to be
an easy process due to the large number of packages (40 or 200,
depending on how you look) and the low level of manpower in the ruby
team, so we think that providing a different set of packages for ruby
1.9.1 (so users can try 1.9.1 and install libs using gems in the
meantime, without removing their 1.9.0 libs and apps) is a better
solution. It increases the maintenance burden on the interpreter side,
but decreases it on the libraries side.
(see the recent thread on debian-ruby@ for the details)
Of course, you are welcomed to help instead of just bitching.
| Lucas Nussbaum
| email@example.com http://www.lucas-nussbaum.net/ |
| jabber: firstname.lastname@example.org GPG: 1024D/023B3F4F |