Ok, so it it looks like the latest version of Merb 1.1 still calls this method (Dsl.load_gem_file). However if it finds the gemenv, it will just load that and continues on before its able to blow up. By default it looks in gems/environment. So as long as thats there, it'll be happy. Otherwise it'll blow up. You can override it by setting Merb::Config[:gemenv]
We should really remove the direct load_gem_file call. Seems like the only approved way to use bundler now is to directly require the generated environment rb file. http://github.com/merb/merb/commit/8cc9b95602fd11f0bec2189e50dde5e161f4a932 On Jan 15, 2010, at 8:56 PM, MarkMT wrote: > Ok, it's a little worse than I thought... > > The merb dependencies bootloader invokes Bundler::Dsl.load_gem_file, > but that method was removed in Bundler 0.8. Back to 0.72... > > Mark. > > > > On Jan 15, 11:37 am, MarkMT <[email protected]> wrote: >> Of course I should have said gems/ruby/<version> , depending on what >> you are using. >> >> MarkMT wrote: >>> Just a heads-up for anyone else who might end up scratching their head >>> over this - it appears that from version 0.8 of bundler (actually >>> 0.7.3.pre) released last week, gems are being bundled into gems/ruby/ >>> 1.8 rather than gems. >> >>> Mark. > -- > You received this message because you are subscribed to the Google Groups > "merb" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/merb?hl=en. > >
-- You received this message because you are subscribed to the Google Groups "merb" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/merb?hl=en.
