I can't comment on the structure without some more information - are those directories named after CPAN modules dependent on those modules? That's not how I would do it myself, but as long as you like it I suppose it's fine. Or maybe they're vendor distributions of the modules, versus your local modifications of those modules. If that's true, then it's a bad idea, for several reasons.

Anyway, I prefer one big repository for all projects, with separate sub-structures for each project. It makes backing up the repository atomically much easier, but you can run into space issues. As always, TIMTOWDI. :)

In reply to Re: How to structure your svn/svk repository by biosysadmin
in thread How to structure your svn/svk repository by badaiaqrandista

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.