You're not using CVS?? I find CVS to 'scale' a lot better, especially when your code gets multiple developers.

You are using h2xs, right? You are using it to make test cases and to install your code properly, right?

At work we use our cvs server for our modules. There is a CVS module called modules (man, that's confusing). In there, we use h2xs, but instead of leaving the directories as Module/Name (for a module called Module::Name), we move it to Module-Name. This prevents "is Module::Name::Alpha a parent or a child?"

So, if you did a cvs co modules you would get a directory structure like this:

modules/Module-Name
modules/DBIx-DSN
modules/XML-Serialized

When you are testing modules, try perl Makefile.pl PREFIX=~/perltest and include that directory in any scripts you use.

cheers.

In reply to Re: Perl code, RCS/CVS, and distribution by DrZaius
in thread Perl code, RCS/CVS, and distribution by Masem

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.