Disclaimer: I’m a Rails newbie, be gentle.
I’ve got an Ubuntu Feisty install here. After adding Ruby and Rails
via Synaptic, I’ve got Rails 1.2.1. To get up to date, I did a “gem
update rails”. So far, so good, AFAICS.
Now when I create a new project (e.g. “rails new-project”), the config/
environment.rb points to Rails 1.2.1 in the RAILS_GEM_VERSION. Worse,
there’s a copy of rails in vendor/rails, and according to rails/info/
properties, it’s 1.2.1.
If I fix the version number in RAILS_GEM_VERSION and unfreeze the
project (rake rails:unfreeze), the project seems to behave as 1.2.3.
But … i’m assuming I shouldn’t have to do that for a new project.
Why’s the project frozen from the get-go, and why is it choosing 1.2.1
when 1.2.3 is available?
I’m totally open to the idea that this is all my fault, but I’m just
not sure why this is happening. Google searches aren’t really
helping. Well, that’s not true, they helped me find the workaround,
but they aren’t helping me find out why this is happening.