What I've done to keep this simple is to just build perl as I would want
it on all server with all of the modules, etc. Then tar up the entire
perl folder and extract it on all of the other servers. Also add
depencies like the arapi folder, other api folders (if needed) into the
same directory structure as on the build server. I've never had a
problem with this procedure.
Brent Bowman
________________________________
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of White, Linn
Sent: Thursday, January 31, 2008 2:25 PM
To: arsperl-users@arsperl.org
Subject: [Arsperl-users] Moving installation between servers
I am currently working on getting ARSPerl installed on one of our lab
servers, and will need to move it to multiple servers once it's tested
and compiled. The issue is that the servers I will be moving to do not
have any compilers on them, so I will have to copy the files over. What
files are created/moved in an ARSperl installation that I will need to
move? Some of them I'm aware of, others I am not.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Arsperl-users mailing list
Arsperl-users@arsperl.org
https://lists.sourceforge.net/lists/listinfo/arsperl-users
