Just to play devil's advocate... If you spend some time reading on the web, and retrieve and install all the pieces and parts yourself, you'll have a much better notion of just what the moving parts are, and you'll know what you have installed when the inevitable gotcha happens. You're forced to learn about what makes up your application and the runtime, and as such, you are not beholden to anyone else to bring your environment up to speed with the next version of whatever widget.
I've followed that tactic with both Windows (early development) and Linux (production) installs, and while frustrating at times, I have a very short list of known players in my application. It made it very simple to migrate from Windows development to Linux production... (and to re-create my development envt in an Ubuntu VMware instance), and to go from Rails 1.2.6 to Rails 2.1.0. -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
