I found out the hard way. I guess some or all of the mirrors don't have
it yet as I am getting 404's Seems like thats a pretty shoddy way to
update. Too bad you can't push it to all of the mirrors before releasing it.
No, both work. Update just removes the previous, while install keeps the previous around. Since Rails apps let you specify which gem to use, this can be quite convenient.
Yes, both work. Greg, the problem you are hitting is not with the
command you are running, but with ruby gems and the repository
problems. I reported this a while ago thinking it was the repositories
not completely in sync with the new rails gems, but it turns out it is
a problem w/ the gem serving system as a whole. According to this post
“It should work now”, but I am getting many failures on many different
gems. Just keep running the commands and they eventually will succeed.
Here is the post
-Bill
Brian Hogan wrote:
I gotta tell ya, it’s been quite a while since I’ve been such a complete n00b: new language, new framework, new tools, complete change in styles all at once – while trying to write non-trivial code as a project. Fun, but the brain is a blender!
Corey, I've been using 1.2.3 for a while and my upgrade to 1.2.6 went
very smooth, just a few deprecation notices related to some route
names.
I need to consume some resources but I don't want to go all the way to
2.0 since some plugins are apparently making my app break. Is there a
way to get ActiveResource working with 1.2.6?