I followed this philosophy for the past year building a platform:

The parts break down into three major categories:
  • our code
  • modules/classes (written in-house, not offered by our OS vendor)
  • 3rdparty items (written outside of our shop, not offered by OS vendor, language independent)

    And this was guided by:
  • our repo containing code should never be mixed with other OPC (other people's code:)
  • our in-house libs/classes should be kept in a dedicated repository easing our ability to release these tools publicly back out into the community
  • addition of 3rdparty or modules would be approved by the Sr Architect after rounds of testing/approval

    Therefore what I came up with was that each of these categories would have its own Subversion repo, and that the group of 3 repos make up the entire "project". There are also requirements for modules (not written in-house, installable in the OS via packaging system), which are kept in a Name/Version list; these are not in a repo.

    My build and deployment system tracks/deploys these parts together for a "release" whose manifest includes the current revision number from each repo.

    -Harold


    In reply to Re: Wondering how to manage cpan modules from within svn projects by hsinclai
    in thread Wondering how to manage cpan modules from within svn projects by dekimsey

    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.