Pancho has asked for the wisdom of the Perl Monks concerning the following question:
Hello Monks,
I’m looking for advice regarding the preferred way to separate the functions of the application team from the server operations (sys admins) team when it comes to managing the perl and perl modules installs in Linux boxes.
Currently, in our prod environment, we use the Perl version that came packaged with the server, and any modules used (i.e. DBD, DBI Oracle etc) are installed by the Sys admins in a directory that they only can modify.
The Sys admins have proposed that the application team, of which I am a part, installs a version of perl and modules that we will used in our own directories and maintain that. The main reason for this being to make the programs as box independent as possible.
Another alternative I can think of is using the lib pragma to point to the modules the app team installs and point to the perl that came packaged with the box.
I like the Sys Admins suggestion because I can control the Perl version and the module installation and you are not at the mercy of whatever gets packaged with the box, but I don’t have that much experience w/ Perl. Can you please advice on the pros and cons of the two alternatives above, or let me know if the ‘standard’ or typical way to resolve this is different altogether.
Thanks in advance,
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re: Seeking Advice re. Managing the perl / modules installs
by hipowls (Curate) on Mar 22, 2008 at 20:38 UTC | |
|
Re: Seeking Advice re. Managing the perl / modules installs
by alpha (Scribe) on Mar 23, 2008 at 02:34 UTC |