Leopard will have Ruby 1.8.6, Rails 1.2.x, Mongel, Capistrano and
Subversion pre-installed as "first-class" citizens into the OS core.
Meaning they don''t live in /usr/local nor /opt directories. I believe
they are installed in /bin. So you shouldn''t have to worry about it
overwriting your installation. Just make sure your install directory
shows up before /bin in the system $PATH environment variable.
That being said, given that Leopard will include nearly the latest
releases of Ruby (and not a broken one) and Rails with most of the
standard goodies, why not just use them. If they are not completely up
to date just use RubyGems to update them. This is what I''ll do once
Leopard is released. Heck as much attention as Apple is putting into
Rails these days, we just might see them upgrade as Rails does with
the standard software update mechanism (one could dream anyway).
On Oct 22, 11:27 am, Josh
<jjkie...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
wrote:> I started using Rails after Tiger came out so I haven''t been
through a
> major upgrade since using it.
>
> I''m a little concerned on what upgrading will do to my development
> environment. I even heard that the new OS would even have Rails
> already installed on it, but I don''t want it to overwrite the
versions
> I have installed already.
>
> Is there any advice and what I need to do in order to prepare for the
> upgrade?
>
> Thanks.
--~--~---------~--~----~------------~-------~--~----~
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
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---