On Feb 21, 2007, at 2:21 PM, Daniel Chudnov wrote:
> I haven't figured out, though, how to most cleanly update frozen gems
> w/r/to the version control repository (svn, in our case).  What's the
> best way to update the gems if, say, you want to go from a set of
> frozen gems from rails-1.1.6 to a new set for rails-1.2.2?

The project I've been working on we just got used to the
churn...since it's not really something that has happened all that
often. But we haven't upgraded versions of Rails yet :-)

I think you could use svn externals to reference third party code.
Mike Clark has a good writeup on piston [1] which supposedly makes
you less reliant on the third party's repository, but still give you
the flexibility of externals. It might be worth looking at.

//Ed

[1] http://clarkware.com/cgi/blosxom/2007/01/22