On Feb 27, 2006, at 6:59 PM, Tyler MacDonald wrote:
#3 seems like the lowest maintenence. Maintaining on a .tar.gz in CVS
seems easier than integrating diffs of the newest version whenever
you want
to upgrade.
We definitely do NOT want to be integrating diffs if we can avoid it.
If we decide to modify a CPAN module (so far we have not) we would
probably check-in the unpacked tarball into our version control (and
probably send a patch to the author :-)
#2 has it's benefits too - you could even mirror all of CPAN, and
just maintain a script with "install" commands to install the
versions you
want;
install "KWILLIAMS/Module-Build-0.27_04.tar.gz";
etc. That makes both upgrading easy and makes your build process
independant from the availablity of your favourite CPAN mirror.
Yes, it also means the build process can take of resolving
dependencies. The downside is having yet-another-repository.
Whatever we do we would like to have a single-step build and release
process:
./build_script.pl --build-number=20060227-001 --environment=QA
and that will deploy both our code AND the CPAN modules we use to the
QA environment (which could be multiple machines.)
-------------------------------------------------------
Matisse Enzer <[EMAIL PROTECTED]>
http://www.matisse.net/ - http://www.eigenstate.net/
