[Rails] The bigger picture

[Curt Sampson]

On Tue, 30 Nov 2004, John Wilger wrote:

> Actually, if you're using proper source-control techniques (especially
> with a more modern SCS such as Subversion, since this doesn't work
> as easily with CVS) copying the library into your project often _is_
> the pefferable way to do things. Do some research on the concept of
> "vendor branches"....

In fact, vendor branches are a bit more difficult with CVS, but not that
hard to deal with once you get the hang of it. I've been doing this for
years. On my current system, for example, I build several C libraries,
apache, php (don't ask), and various php and ruby libraries (incuding
ActiveRecord) from source I keep in CVS with the rest of my project, and
I've been considering even moving ruby in there. This ensures that I'm
testing and deploying my system on the same support code.

This, BTW, is a very good reason for keeping available non-gems versions
of things like rails. Having stuff available only in another package
management system forces me to unpackage it so that I can "re-package"
it in my system.

cjs
-- 
Curt Sampson  <cjs at cynic.net>   +81 90 7737 2974   http://www.NetBSD.org
     Make up enjoying your city life...produced by BIC CAMERA