[Mongrel] mongrel startup fails now: already initialized constant OPTIONS
evan at cloudbur.st
Thu Nov 15 16:10:43 EST 2007
No aspersions cast on Zed but I hate gem_plugin, and the team is
planning to remove it in a couple months. We just need a temporary
hack for now so that Ruport isn't busted.
On Nov 15, 2007 3:41 PM, Stephen Bannasch
<stephen.bannasch at deanbrook.org> wrote:
> Gregory Brown, the developer of Ruport reports:
> At 8:02 AM -0500 11/15/07, Gregory Brown wrote:
> >Okay, after digging through all of this it sounds like Rails /
> >GemPlugin are trying to autoload the ruport gem itself even though it
> >isn't a plugin (has no init.rb). This to me sounds like Rails is
> >abusing gem_plugin, because Ruport does not depend on rails and thus
> >should not be loaded.
> >That having been said, Ruport 1.0 on up don't explicitly depend on
> >gem_plugin, so it won't be detected by Rails, and thus won't break. (I
> >If you have versions 0.8.10 -> 0.8.14 laying around and are
> >experiencing this problem, try deleting them.
> >Also, thanks for pointing this problem out, I've seen it before but
> >only in weird cases, and was wondering what happened.
> Sounds like it could be a problem with gem_plugin, or interactions between gem_plugin and rails, or gem_plugin ,rails, mongrel, ruby 1.8.6, and ruport <1.0
> Mongrel-users mailing list
> Mongrel-users at rubyforge.org
More information about the Mongrel-users