From: Alder Green <alder.green@...>
Date: 2006-04-17T02:48:39+09:00
Subject: Re: Bug: Requiring "breakpoint" causes the entire Rails framework to load.

On 4/16/06, Logan Capaldo <logancapaldo@gmail.com> wrote:
>
> On Apr 16, 2006, at 1:09 AM, Alder Green wrote:
>
> > In the short-term, is the best solution to simply get ruby-breakpoint
> > not through gems?  Or is there a way to fix this issue while still
> > using the convenient gem version?
> >
>
> I think maybe if you know the version of ruby-breakpoint and its not
> the same as the rails one you could try something like
> require 'rubygems'
> require_gem 'ruby-breakpoint', '0.5.0'
> require 'breakpoint'

Hi Logan

Thanks, your solution worked. "require_gem 'ruby-breakpoint', '0.5.0'"
did in fact load only the 0.5.0 did in fact load only the
ruby-breakpoint 0.5.0, and not the ruby-breakpoint bundled with Rails
(whatever it is; I know not how to determine).

However, on a permanent basis I'll probably use Florian Gro�'s
solution, which works as well: copying the two ruby-breakpoint rb
files to site_ruby. This solution allows me to require ruby-breakpoint
in the standard way ("require 'breakpoint'") and saves me the trouble
of keeping track of my current ruby-breakpoint gem version and more
importantly: of the Rails gem version, naturally worrying that one day
it might catch up with the gem and bring back the problem I raised
here.

I'm going to raise the issue in the Rails bug tracking system. Looks
like their work is cut out for them - no appearant reason why they
can't use the proper way, i.e. remove the bundled breakpoint.rb file
and add the ruby-breakpoint gem.

However, this thread seems to raise an name-clashing issue which
perhaps should be brought to the attention of RubyGems' architects.

Regards,
Alder