|There's more than one way to do things|
CVS CGI & Perlby mandog (Curate)
|on Jun 02, 2002 at 20:48 UTC||Need Help??|
mandog has asked for the
wisdom of the Perl Monks concerning the following question:
I'm a few chapters into Open Source Development With CVS The good bits of the book are released here under the GPL
Our (student & wannabe, hobbyest and unemployed) crew wants to get into CVS for a bunch of reasons. Our current method of version control is: "copy the current file to the "old" folder with today's date as a suffix." We want to know enough CVS to start contributing to projects like nms-cgi Our patron at the university wants his students to learn CVS. Often we'll go weeks without working on the code and then forget where we were (no changelog). We don't really have a boundary between production and development code. We're using emacs instead of pico now, but people still don't tell us we are cool.
We've built a couple simple modules. (Now in /usr/local/lib/perl5/site_perl/) and apart from canned scripts, will mostly be doing CGI/DBI stuff.
We have our own machine(s) I'm wondering the best way to set things up and I'm wondering what tips people have for using CVS with Perl & CGI programs.
I'm thinking of modifying our existing setup to be something like:production space:
Developer space would replace:
Does this setup make sense?
Anybody got some general CVS / Perl / CGI / CPAN (??) tips?