On Fri, Aug 01, 2008 at 08:23:02AM -0000, Neil Wilson wrote:
> Linking to /usr/local/bin sounds appealling until you do the following
> rather reasonable sequence of events.
>
> Install 1.8 Gem
> Install 1.9 Gem
> Uninstall 1.8 Gem.
>
> Result is no link in /usr/local/bin and the user installing gem from
> source again 'cos those packages don't work properly'.
I'm not sure I understand what you're referring to with 'packages' -
the rubygem package ?
What does the "gem from source" do ? Install in /usr/bin/ ? In
/var/lib/gems/ruby1.{8,9}/bin ? How does "gem from source" handle the
scenario you've outlined above ?
> However that doesn't get away from the problem of dpkg packages failing
> to inform gem that they exist so that gem pulls (and compiles!) gems it
> doesn't really need. That discussion is probably a separate bug.
On Fri, Aug 01, 2008 at 08:23:02AM -0000, Neil Wilson wrote:
> Linking to /usr/local/bin sounds appealling until you do the following
> rather reasonable sequence of events.
>
> Install 1.8 Gem
> Install 1.9 Gem
> Uninstall 1.8 Gem.
>
> Result is no link in /usr/local/bin and the user installing gem from
> source again 'cos those packages don't work properly'.
I'm not sure I understand what you're referring to with 'packages' -
the rubygem package ?
What does the "gem from source" do ? Install in /usr/bin/ ? In gems/ruby1. {8,9}/bin ? How does "gem from source" handle the
/var/lib/
scenario you've outlined above ?
> However that doesn't get away from the problem of dpkg packages failing
> to inform gem that they exist so that gem pulls (and compiles!) gems it
> doesn't really need. That discussion is probably a separate bug.
Agreed. Feel free to open a new bug.
-- www.ubuntu. com
Mathias Gug
Ubuntu Developer http://