comment on

In my department we are transitioning to maintaining our own installation of Perl and its bevy of modules.

In the hopes of making this process simpler, we're making use of perlbrew. It feels quite promising so far. Our previous module setup was complex and has gotten messy since the person who maintained it left.

To install modules into my test environment, I've been using cpanm to install from public CPAN, but am using the older cpan shell in cases where I have to apply patches using distroprefs (which I just learned how to do).

We have a couple of environments that require a very limited set of modules, and we're looking at using Pinto for those.

Our transition is far from complete: one of the things we're trying to determine is the best place to put our in-house modules. My first impulse was just to hand-create a subdirectory under site-perl and simply plunk the modules there, but I'm now thinking I should query wiser, more experienced heads before doing so.

In reply to Re: How Do You Manage Your Perl Modules? by chexmix
in thread How Do You Manage Your Perl Modules? by jthalhammer

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.


No such thing as a small change
	PerlMonks