On 01/06/08 at 14:29 +0200, Paul van Tilburg wrote:
> Package: ruby1.9
> Version: 1.9.0.1-1
> Severity: grave
> Justification: renders package unusable
>
> The Ruby 1.9 interpreter in Debian uses /usr/lib/ruby/1.9.0 instead of
> /usr/lib/ruby/1.9 as system base in the $LOAD_PATH. Since all -ruby1.9
> packages install to the /usr/lib/ruby/1.9 directory, they are all
> unusable!
from ruby1.9's NEWS.Debian file:
ruby1.9 (1.9.0.0-1) unstable; urgency=low
$LOAD_PATH is changed in Ruby 1.9.0-0 as the following:
["/usr/local/lib/site_ruby/1.9.0",
"/usr/local/lib/site_ruby/1.9.0/i486-linux",
"/usr/local/lib/site_ruby/1.9/i386-linux",
"/usr/local/lib/site_ruby",
"/usr/lib/ruby/vendor_ruby/1.9.0",
"/usr/lib/ruby/vendor_ruby/1.9.0/i486-linux",
"/usr/lib/ruby/vendor_ruby",
"/usr/lib/ruby/1.9.0",
"/usr/lib/ruby/1.9.0/i486-linux",
"/usr/lib/ruby/1.9/i386-linux",
"."]
This changes was introduced because Ruby 1.9.1 (or later version) may be
incompatible with this version of Ruby. If you have libraries in old
$LOAD_PATH, please rebuild it with this version of ruby1.9-dev package.
-- akira yamada <[EMAIL PROTECTED]> Wed, 26 Dec 2007 10:34:48 +0900
It's not a Debian change, it's an upstream one.
Such a layout only makes sense if someone want to coinstall ruby 1.9.0 and ruby
1.9.1: if we have only one dir (for 1.9), then won't be able to install two
versions of the same lib (one for 1.9.0, one for 1.9.1). On the other hand, if
a lib was ported to 1.9.0, it's likely to be easy to port from 1.9.0 to 1.9.1.
So we could probably do that as Debian-specific changes if necessary.
I think that this should be raised on ruby-dev@ (others are likely to run into
the same problem). Akira-san, Daigo-san, could one of you ask for the Ruby
developers' opinion?
--
| Lucas Nussbaum
| [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ |
| jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F |
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
