Hi, I've had a few problems with bundler since upgrading rubygems to 1.3.6. I was previously using bundler 0.7.2 but after upgrading rubygems got some weird error messages about #join not being defined on some path strings. This persisted with bundler 0.8.1. I tried 0.9.7 and 0.9.11, but for some reason gem didn't seem to even recognize their presence on my machine - I got a message saying that the bundle command wasn't recognized.
Eventually I tried installing bundler08 v0.8.5, and this seems to have worked. However I notice that in the process of bundling my gems, bundler 0.9.11 has been added to the application bundle, presumably through merb-core's dependency specification. I have yet to try and push this out to my production machine, but I have a suspicion this isn't going to work. For one thing my production machine is still running rubygems 1.3.5, but even if I update it, is it going to work with bundler 0.9.11? I see Pavel's note here that he is using bundler 0.9.7 - http://groups.google.com/group/merb/browse_thread/thread/d10d62e76803af4f/c34f780311baa6e5?lnk=gst&q=rubygems#c34f780311baa6e5 I'm curious how that is working out - as I say I haven't had any success with 0.9.7. I see that the gemspec for merb-core-1.1.0.pre has a dependency on bundler ">= 0.7.2", but (i) in my experience neither 0.7.2 nor 0.9.x work with rubygems 1.3.6, and (ii) this dependency isn't satisfied by bundler08 even though that does work with 1.3.6. So I'm trying to figure out what to do: should I tweak the merb-core gemspec to depend on bundler08 instead of bundler, or should I just drop back to rubygems 1.3.5? Or am I just confused?! How is everyone else currently setting up their applications? 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.
