I'm not sure why it prefers the oldest version, but the mongrel_cluster_ctl script effectively runs:
require_gem "mongrel_cluster", "> 0" which seems like it would prefer the oldest. reading the script a tad more, it looks like you can specify which version to run by passing in _VERSION_ (e.g. _1.0.5_) as the first argument to mongrel_cluster_ctl On Mar 5, 2008, at 12:29 PM, Jonathan Rochkind wrote: > Okay, you're right. That did work, I didn't do a good job of removing > mongrel_cluster-1.0.2 before. The question still remains, why the heck > do I need to actually REMOVE 1.0.2 to get mongrel 1.1.4 to use it, > when > there's a newer mongrel_cluster 1.0.5 installed? This shouldn't > actually > be, should it? Aren't you supposed to be able to have both > installed in > gems at once? Anyone have any explanation for why mongrel was > preferring the older one when both were installed? [It's this kind of > thing that drives me nuts with ruby/rails, especially with deployment > issues]. > > Now that I've gotten it to use mongrel_cluster 1.0.5, > mongrel_cluster_ctl is indeed properly dealing with the --clean > argument, that bug is gone. > > Very frustrating. Thanks for the help all. Still plan to submit a > patch > for the resources/mongrel_cluster script to use --clean. Does this > make > sense? That resource/mongrel_cluster script is mentioned in the > mongrel_cluster README still, so it does seem like it's supposed to be > still a non-deprecated thing? _______________________________________________ Mongrel-users mailing list Mongrel-users@rubyforge.org http://rubyforge.org/mailman/listinfo/mongrel-users
