Sounds like a shell PATH issue: you'll want to set up your $PATH such that cap 2.5.5's path precedes cap 2.5.3's path -Erik
On Tue, Mar 31, 2009 at 6:43 PM, Wayne Soh <[email protected]> wrote: > > Hi, > > I'm not sure whether this is exactly a gem question or a capistrano > question. > > I have a linux set up with gem_path set as /usr/local/lib/ruby/gems/ > 1.8 and capistrano 2.5.5 installed to that directory. However, I > realized that there's an old version of capistrano 2.5.3 installed to > the /usr/lib/ruby/gems/1.8 directory and doing a cap calls capistrano > from the latter directory. This is causing a problem with some of the > requires that I'm using in config/deploy. > > Is there a reason why cap is being pulled from the location not > specified as a gem path?? > > Thanks > Wayne > > > > --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
