comment on

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're using perl entirely for CGI and system administration for our web site and for the web sites of other organizations.

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:

# not in CVS
/home/sites/<sitename>/cgi-bin  

# not in apache webspace & not in CVS
        # for .ini style files
/home/sites/sitename/config/

# In CVS & in Apache webspace, one CVS projects per dir 
/home/sites/<sitename>/cgi-bin/project_1/ 
/home/sites/<sitename>/cgi-bin/project_2/

# In CVS out of apache webspace, one CVS project per dir
/home/sites/<sitename>/lib/mod_1/
/home/sites/<sitename>/lib/mod_2/
[download]

Developer space would replace:

/home/sites/<sitename>
[download]

with:

/home/people/<person>public_html/
[download]

Does this setup make sense?

Anybody got some general CVS / Perl / CGI / CPAN (??) tips?

email: mandog

In reply to CVS CGI & Perl by mandog

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Your skill will accomplish what the force of many cannot
	PerlMonks