Re: Problem upgrading to Rails 2.3.2

> Hi Erno,
>
>
>
> Thanks for your interest in this matter. It turns out that is a relative pain in the *&^% to upgrade Rails if you've vendored it in your project directory. The culprit? Subversion.
>
>
>
> Most books/forums/blogs simply discuss how to originally freeze Rails. But when you go hunting for problems with upgrading Rails that's under Subversion source control - well, you quickly find out you are not alone.
>
>
>
> After reading a bunch of posts, and for a number of my own reasons, I decided to no longer vendor Rails, i.e. I simply use the gems that are located in my Ruby installation.
>
>
>
> Thanks again, Erno.
>
>
>
> -- Larry
>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>
>