Comment 5 for bug 145267

Kevin DuBois:

> perhaps it would be better to have the package install symlinks to
> directories already in $PATH or to modify the build the package so
> that it is installed to somewhere in $PATH

The catch is, Debian/Ubuntu doesn’t control the files that can come in
the installed gems, so can’t assure there aren’t any clashes in their
filenames (I can easily create a gem that will ship a ‘cp’ binary
and upload it to RubyForge) – hence RubyGems can’t symlink files in
/var/lib/gems/1.8/bin from any dpkg-handled location.

(Now that I look at my $PATH, it seems /usr/local/bin is there by
default, so maybe symlinks from there would make it all work. Still,
adding /var/lib/gems/1.8/bin somehow to the $PATH seems the better
solution – although I know it’s not simple to implement.)

-- Shot
--
Like most computer techie people, I'll happily spend 6 hours trying to
figure out how to do a 3 hour job in 10 minutes. -- James Cort, asr