mostly what we develop is online applicaiton under solaris 8 or 10, Perl 5.8.7.

we are in process of introducing standards to our Perl development ( Perl is still relative new in this place ) . currently, the unix group supplies us a separate Perl under /usr/local/ and install every requested module for us into that tree. their support has been lacking due to the our usage of Perl going up. We often have to wait for weeks to have something installed.

thus, I am trying to find better way to manage modules by ourself. we have modules from CPAN, modules written by me and others.

been searching around, I have found some ideas from the following nodes.

  • Management of perl modules in enterprise?
  • Professional development with Perl - how it's done?
  • Maintaining an Enterprise Perl Distribution

    to summary a bit:

    1. have a centralized place to hold all modules. use rsync or cvs to keep the modules up-to-date among servers.

    2. build apps with all their libraries local. keep track of which app use what version of the module. update module case-by-case. such as krang

    I am leaning toward the option 1. because having modules in one place seem to cleaner and easy to manage. my guess is that there won't be many module upgrades. if there is a major bug fix or a necessary feature for a module, we test it out on Dev, QA then roll it out to production.

    in the end, if we have perl modules under /team/perl_lib/, we can just include that path in the "use lib '/team/perl_lib'; ".

    that's fine for pure perl module. but i am uncertain how to deal with the XS module that required to compile. I am thinking about building XS modules in a desinated location and then copy it to the central Perl library dir. however, try building Text::CSV_XS today, the binary is stored under /build_dir/lib/perl5/site_perl/5.8.7/sun4-solaris/auto/Text/. the Perl module is installed under /build_dir/lib/perl5/site_perl/5.8.7/sun4-solaris/Text/. how do i mix it with the pure Perl modules and still be able to use 'use lib '/team/perl_lib' ?

    i am also interested in your take on module managment.. which method do you prefer and why?

    In reply to module management in enterprise? by Qiang

    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.