I'm working on CAD::Drawing, which now is up to about 17 modules.  I'm also 
talking to the author of perlcad (really new project) about collaboration, so 
there will be a need for CVS (actually, I'm leaning toward subversion 
(subversion.tigris.org.)

So, how to develop multiple inter-related perl modules using CVS?  Anyone have 
links to howtos or case studies of this?

Specifically, I'd like to be able to checkout the module tree directly into 
one of the @INC directories so that changes can be immediately tested rather 
than having to jumping between 17 build directories and doing 'make clean && 
perl Makefile.PL && make && make test && make install' for each one as it 
changes.

I could see keeping all of the Makefile.PL and associated stuff under one 
tree, and directly installed modules under another, but this would require 
some kind of script to merge the two together in order to build a release and 
upload to CPAN.

I don't want to keep everything in one build tree, because many of the modules 
are optional, and new versions should be uploadable as individual packages.

Any suggestions?

Thanks,
Eric

Reply via email to