Beefy Boxes and Bandwidth Generously Provided by pair Networks
more useful options
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??

I just wanted to get some guidence from the monks on the placement of perl modules, standard and home grown. I maintain perl on just a couple of machines and I do most of the coding in the unit myself. I currently have the standard modules installed on each workstations C: drive (WinXP, ActiveState 5.6.1). I also have a general home grown module library contained on a network drive. I add the lib to the path at the start of those programs that need it. I have it set up this way to keep from having to push the changes to these libraries to each individual machine. They are in active development and change frequently.

The set up seems a little kludgy to me in that, whenever I add modules to my own workstation during development, I have to remember to go to each workstation and load those modules to it. Too often I forget, or miss one. How embarrasing

I have, occasionally, considered moving the entire Perl library out to a network drive so that I could update once for everyone. However, it seems the windows setup wants to be installed on the local machine and I am unsure as to how difficult it would be to change things.

Has anyone had any experience trying this on a Win32 platform?
Update:
Thanks for the great suggestions. It seems like one or more of them will meet my needs. Thanks again.

PJ
use strict; use warnings; use diagnostics;

In reply to A Home For Perl Modules by periapt

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 pondering the Monastery: (3)
As of 2024-04-26 05:01 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found