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?
Mark. On Mar 12, 10:08 am, Paul Dlug <[email protected]> wrote: > On Fri, Mar 12, 2010 at 10:56 AM, MarkMT <[email protected]> wrote: > > A little progress with this... I realized the reason gem didn't > > recognize bundler 0.9.x is that the command has changed from 'gem > > bundle' to 'bundle install'. And I need to 'bundle pack' first to > > populate vendor/cache. Ok. > > > But bin/merb no longer exists. What's the right way to start the > > bundled app? > > The right way is now to use bundle exec, for example "bundle exec merb ...". > I haven't yet been able to get merb 1.1 playing nicely with the latest > bundler but this seems mostly due to a dependency ordering issue affecting > DataMapper where gems like dm-timestamps are included before dm-core. > There's an open issue on it in the bundler queue, just waiting for things to > stabilize a bit more before I attempt it again. > > Good luck, if things are working better than the last time I tried > definitely let me know. > > --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.
