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

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.