Ubuntu
libgems-ruby package

RubyGems install path prevents mongrel from being a recognized command

Bug #116237 reported by Jared Brown on 2007-05-22

Affects		Status	Importance	Assigned to	Milestone
	libgems-ruby (Ubuntu)	Invalid	Undecided	Unassigned

Bug Description

Binary package hint: rubygems

When using RubyGems installed through Synaptic, running "sudo gem install mongrel" places mongrel_rails under /var/lib instead of /usr/bin and /usr/lib, thus preventing users from easily running it via their environment paths. The immediate work around is to download and install RubyGems from the official site.

Revision history for this message

Timo Derstappen (teemow) wrote on 2007-05-22:

I can confirm this bug. gem executables end up in /var/lib/gems/1.8/bin. Work arounds are symbolic links in /usr/local/bin or adding /var/lib/gems/1.8/bin to PATH.

Revision history for this message

Jared Brown (jaredbrown) wrote on 2007-05-22: Re: [Bug 116237] Re: RubyGems install path prevents mongrel from being a recognized command

I would be very helpful if there was no need for a work around after
installing RubyGems

On 5/22/07, teemow <email address hidden> wrote:
>
> I can confirm this bug. gem executables end up in /var/lib/gems/1.8/bin.
> Work arounds are symbolic links in /usr/local/bin or adding
> /var/lib/gems/1.8/bin to PATH.
>
> --
> RubyGems install path prevents mongrel from being a recognized command
> https://bugs.launchpad.net/bugs/116237
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Jared Brown
<email address hidden>
(765) 409-0875
7001 Central Ave
Indianapolis, IN 46220

Revision history for this message

Neil Wilson (neil-aldur) wrote on 2007-08-07:

This is working as designed.

Ubuntu rubygems is derived from Debian rubygems, and both of them deliberately place the gem executables into /var/lib/gems/1.8/bin. It is a matter of policy

See the README.Debian file at /usr/share/doc/libgems-ruby1.8/README.Debian

You have to place /var/lib/gems/1.8/bin on your PATH in your .bashrc and then everything works fine.

Changed in libgems-ruby:
status:	New → Invalid

Revision history for this message

Ryan Maki (ryan.maki) wrote on 2007-09-15:

I've just wound up filing a duplicate of this bug.

Perhaps we could find a way to inform users at installation that they need to alter their $PATH, just so they don't wind up confused enough to file a bug report, as I just did. Thanks.

Revision history for this message

Jared Brown (jaredbrown) wrote on 2010-04-08: Hello

http://sites.google.com/site/ghjkkuiy65y/vset5w