Beefy Boxes and Bandwidth Generously Provided by pair Networks
Don't ask to ask, just ask
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
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":



    • 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.
  • Log In?
    Username:
    Password:

    What's my password?
    Create A New User
    Domain Nodelet?
    Chatterbox?
    and the web crawler heard nothing...

    How do I use this?Last hourOther CB clients
    Other Users?
    Others exploiting the Monastery: (3)
    As of 2024-03-19 05:15 GMT
    Sections?
    Information?
    Find Nodes?
    Leftovers?
      Voting Booth?

      No recent polls found