I'm sure Jan will correct me if I'm wrong, so... IIRC a perlapped .exe will use "installed" modules instead of the compiled-in modules (according to the normal @INC handling). You should be able to "install" modules on the servers, and use the --exclude option on perlapp to make your .exe smaller. - - Martin
> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Daniel Rychlik > Sent: Monday, June 26, 2006 18:21 > To: David Nicol > Cc: [email protected] > Subject: RE: Perl Includes? > > Part of the reason this isn't feasible is because about 85% > of our servers are on a dial up connection. We like to keep > our conversations to a minimum due to the cost associated > with making numerous long distance calls to each of these > servers. I have to keep up with modems in my core code as > well as all the remote execution of the remote tools. > > > It would be nice to just compile the DBI module, put in the > remote upload queue, copy it once, and then modify to the use > DBI part of the program to include the DBI module upon > program execution. That way I wouldn't have to compile my > perl scripts with the DBI module wrapped in it. That is > about 1.2 MB of my programs and when you have 7 remote > programs that you are executing, it really helps to keep them > as small as possible. > > > > -----Original Message----- > From: David Nicol [mailto:[EMAIL PROTECTED] > Sent: Monday, June 26, 2006 5:14 PM > To: Daniel Rychlik > Cc: [email protected] > Subject: Re: Perl Includes? > > 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 > _______________________________________________ ActivePerl mailing list [email protected] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
