On Fri, Mar 12, 2010 at 12:16 PM, MarkMT <[email protected]> wrote:
> Thanks Paul. I tried your suggestion, but what I see is that ./gems/ > bin/merb is executed, but it invokes all the system gems instead of > the bundled versions. Previously, there was a ./gems/environment.rb > file require'd that added the bundled gems to the loadpath, but that > doesn't seem to be used anymore. How are the bundled gems now supposed > to be loaded? > Which version of merb are you running? If it's 1.1 it should "just work" with the new style of bundler, if it's older than that you'll run into other issues with dependency loading deeper in the merb gems. The environment.rb is now only created after running "bundle lock" and is in .bundle/environment.rb, if you run unlocked it will use the system gems unless you do something like "bundle install vendor" to put the gems into the vendor subdirectory. Again, this will only really work with merb 1.1. --Paul -- 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.
