I think this is some great advice that isn't really out there at the moment!
merb:dependencies:install definitely needs a bit of work. i struggled this morning trying to bundle the gems from the nightly gem server, but couldn't figure out a way (without adding the server as a global source) to use the nightly server with merb:dependencies:install. As I couldn't get it to do what I wanted I just used merb:gem:install --cache, to install from my local gem cache. Is there a way to specifiy the gem sources for merb:gem or merb:dependencies? Would it make sense to have the --cache option for merb:dependencies:install? Does it make sense to remove the merb:dependencies tasks for release? and put the back in when the kinks are removed? On Thu, Nov 6, 2008 at 1:43 PM, Yehuda Katz <[EMAIL PROTECTED]> wrote: > at this point we're not really recommending the use of > merb:dependencies:install because we haven't worked the kinks out (and > probably won't before 1.0). Instead, use merb:gem:install, which you can use > to install individual gems. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
