Rails - Aug 2006 - Developing in different versions of rails at the same time?

Hi,
I was wondering if some of you have had to keep more than one version of 
Rails on your machine at a time?  If you have more than one customer, 
they may have different requirements.  You might need to work on a 
pre-existing app that is not scheduled to be moved to a newer version of 
Rails right now.  How is the best way to deal with this?

thanks,
jp

-- 
Posted via http://www.ruby-forum.com/.

I have no experience with that kind of situation but maybe you''ll want
to
setup a VServer solution if you are on Linux.

http://linux-vserver.org/

regards!

Guillaume Carbonneau

On 8/16/06, Jeff Pritchard <jp@jeffpritchard.com>
wrote:
>
> Hi,
> I was wondering if some of you have had to keep more than one version of
> Rails on your machine at a time?  If you have more than one customer,
> they may have different requirements.  You might need to work on a
> pre-existing app that is not scheduled to be moved to a newer version of
> Rails right now.  How is the best way to deal with this?
>
> thanks,
> jp
>
> --
> Posted via http://www.ruby-forum.com/.
> _______________________________________________
> Rails mailing list
> Rails@lists.rubyonrails.org
> http://lists.rubyonrails.org/mailman/listinfo/rails
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://wrath.rubyonrails.org/pipermail/rails/attachments/20060817/81d0f742/attachment.html

Guillaume Carbonneau wrote:
> I have no experience with that kind of situation but maybe you''ll
want
> to
> setup a VServer solution if you are on Linux.
> 
> http://linux-vserver.org/
> 
> regards!
> 
> Guillaume Carbonneau
Thanks Guillaume,
Should have mentioned obviously the OS.  I''m on OSX.

thanks,
jp

-- 
Posted via http://www.ruby-forum.com/.

On 8/16/06, Jeff Pritchard <jp@jeffpritchard.com>
wrote:
> Hi,
> I was wondering if some of you have had to keep more than one version of
> Rails on your machine at a time?  If you have more than one customer,
> they may have different requirements.  You might need to work on a
> pre-existing app that is not scheduled to be moved to a newer version of
> Rails right now.  How is the best way to deal with this?
>
> thanks,
> jp
Freeze the app to the version of rails it''s  developed for.  There are
two good tasks:

rake rails:freeze:gems
rake rails:freeze:edge

Also you can freeze based on release tags, edge rails, or the stable branch:

http://dev.rubyonrails.org/svn/rails/tags/
http://dev.rubyonrails.org/svn/rails/trunk/
http://dev.rubyonrails.org/svn/rails/branches/stable/

svn co http://dev.rubyonrails.org/svn/rails/tags/rel_1-1-6/ vendor/rails

-- 
Rick Olson
http://weblog.techno-weenie.net
http://mephistoblog.com