Comment 50 for bug 145267

2008/8/14 Mathias Gug <email address hidden>:
> I was using the progressbar example from the rubygems documentation[1]:
>
> The command 'ruby test.rb' fails with a "no such file to load -
> progressbar" error message.

I'm betraying my Rails heritage here and giving you duff instructions.

On Ruby1.8 with a pure ruby application you always have to start a program with

require 'rubygems'

to get the 'require' monkey patching in place so you can use gem
libraries. In ruby1.9 that is done automatically.

(f you work in the Rails framework then Rails does that for you).

So you don't need the symlinks and rubygem1.8 users wouldn't expect
them to be there.

> Other comments on the diff between 1.2.0-2 and
> 1.2.0+2008081301-0ubuntu1~bbox1:
>
> * debian/control:
>
> You've modified the build-dependencies - you're depending on rdoc
> rather than an explicit version of it. I think keeping the
> dependencies as close as possible to the ones in debian would help.

Isn't it a packaging bug? There is no need for a specific version so
it should depend upon the default package. I understood that to be
Ruby policy.

> ruby-pkg-tools has been dropped - why ?

Not used.

> rubygems depends on rubygems1.8 *and* ruby. The dependency on ruby
> seems redundant.

It does until you have a clean machine and do 'apt-get install
rubygems' at which point you would have access to 'gem', but not
'ruby'. '/usr/bin/ruby' is controlled by the ruby package.

If I've installed rubygems without a suffix I sort of expect to be
able to use ruby without a suffix.

Similarly if I've install rubygems1.8 I'd sort of expect ruby to be
called ruby1.8 - hence why the dependency is here and not in the
rubygems1.8 package.

--
Neil Wilson