On 6/26/06, Daniel Rychlik <[EMAIL PROTECTED]> wrote: > we don't want to install > Perl on each of the 1200 servers that we update. Transferring this amount > of data X 7 is not feasible every time I need to change a Perl program to > include new tasks. My question is, how I can compile the DBI module into > its own executable and when I copy the new Perl program, when I use DBI in > each program it will include the DBI module, which is compiled that is > already located on the remote site.
My initial response to this is to wonder if a suitable workaround might be to set up some kind of centurion/soldier system at each of your fewer than 1200 sites, so that the distribution goes to the centurion who is then responsible for updating its soldiers. Why can't you install perl on the servers? Maybe this policy can be changed. -- David L Nicol E-mail is legendarily opaque to nuance and it becomes less so only with continuous honest feedback. _______________________________________________ ActivePerl mailing list [email protected] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
