Comment 43 for bug 145267

I've reviewed the libgem-ruby package from the ubuntu-ruby ppa
(libgems-ruby_1.2.0+2008072001-0ubuntu1~bbox4). Here are my comments:

On Mon, Aug 04, 2008 at 11:43:26AM -0000, Neil Wilson wrote:
> New version in https://edge.launchpad.net/~ubuntu-ruby/+archive
>
> - It's ready for the other ruby interpreters that are around the corner - Jruby and Rubinus.

How so ?

> I think this is now the release candidate. Feedback please.
>

===
You've switched to cdbs simplepatch system and it seems you've removed a
  couple of patches in the process:

 01_default_gem_path.dpatch
 03_disable_update_system.dpatch
 08_tighter_search_regex.dpatch
 21_avoid_ioseek.dpatch

Are these no longer required ?

===
You should merge the latest version of debian (-2) as your package is
currently uninstallable on intrepid.

===
While testing the package I came across the usage of gem libraries:
according to the rubygems documentation, you need to do some
post-install work in order to setup ruby gems correctly. I was wondering
if the ruby libraries could be symlinked to
/usr/local/lib/site_ruby/RUBY_VERSION/ when a gem is installed ? That
way you wouldn't have to modify your environment or call ruby with the
-rubygems option. Since site_ruby is already versioned
update-alternatives is not needed in that case.

===
I've also come across the following situation:

 $ sudo gem1.8 install rails
 $ sudo gem1.9 install rails
 $ sudo gem1.8 install rails

However /usr/local/bin/rake is still using ruby1.9. So gems dependencies
are not switched to the ruby version used by the installed gem. Is this
a valid use case ? How should it be handled ? Could the slave option of
update-alternatives be used to handle binaries from dependencies ?

--
Mathias Gug
Ubuntu Developer http://www.ubuntu.com