[DRE-maint] Bug#637914: rubygems1.8: overwrites scripts installed by gem1.9.1 (and vice versa).

[Matijs van Zuijlen]

Package: rubygems1.8
Version: 1.7.2-1
Severity: normal

Hi,

Rubygems 1.8 and 1.9.1 now install scripts in the exact same location. This
means that, depending on the order in which this is done, install the same
gem with both versions leads to an executable that eather runs with ruby
1.8 or with ruby 1.9.1. This can be extremely confusing.

For example, at some point I had bundle running with 1.8 and rake running
with 1.9.1 (without knowing this, of course). The result was, that in a
Rails project

  rake -T

would claim some gem wasn't installed, whereas

  bundle exec rake -T

would run fine.

Can we please have two different locations again? Since rubygems is
considered a developer tool from the viewpoint of Debian, it should not be
too much to ask to have the user or system administrator put the desired
version in the path.

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.0.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages rubygems1.8 depends on:
ii  rubygems                      1.7.2-1    package management framework for R

rubygems1.8 recommends no packages.

rubygems1.8 suggests no packages.

-- no debconf information