Comment 5 for bug 228345

The gem command *is* a completely integral part of ruby1.9. Removing
it is like removing the standard library or the interpreter itself.

There is a great need to start treating gem with the respect that ruby
developers expect, rather than this continuing attempt to treat it as
some sort of side issue. It's like trying to hold back the tide and is
already causing massive problems in using both Debian and Ubuntu as a
basis for any sort of Ruby operation. It's deeply frustrating.

Every serious ruby developer has gem installed. Every serious ruby
program going forward will use gems. I see no value at all in
splitting it out.

2008/5/16 Lucas Nussbaum <email address hidden>:
> On 16/05/08 at 12:36 -0000, Ubuntu Merge-o-Matic wrote:
>> Changes:
>> ruby1.9 (1.9.0.1-1ubuntu1) intrepid; urgency=low
>> .
>> * Merge from debian unstable, remaining changes:
>> - Robustify check for target_os, fixing build failure on lpia.
>
> OK, will merge that one in the Debian package.
>
>> * debian/control:
>> - ruby1.9 pkg: moved rdoc1.9 suggestion to depends. (LP: #228345)
>
> That's wrong. The right solution is to make gem1.9 not part of ruby1.9.
>
> The consequence of your change is that every user of an app written in
> ruby (1.9) now installs an additional and useless (for them) 1MB package.
> --
> | Lucas Nussbaum
> | <email address hidden> http://www.lucas-nussbaum.net/ |
> | jabber: <email address hidden> GPG: 1024D/023B3F4F |
>
> --
> gem1.9 - require 'rdoc/template' fails - missing dependency
> https://bugs.launchpad.net/bugs/228345
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Neil Wilson