Re: MSA rewrite project
Roger Burton West wrote: [feasibility of putting .pm files next to a script] > I believe IIS does horribly evil things to the current execution > directory. I wouldn't be surprised. I believe it also does funky things with %ENV, such that you can't do 'keys %ENV' and get all the keys, as somehow, some keys are only put into the environment when you first access them for reading. Or something. Cheers, Philip -- Philip Newton <[EMAIL PROTECTED]> All opinions are my own, not my employer's. If you're not part of the solution, you're part of the precipitate.
Re: MSA rewrite project
On or about Tue, Mar 13, 2001 at 05:34:03PM +0100, Philip Newton typed: >Generally, @INC contains '.', so it should work (though remember that >Net::SMTP has to go into ./Net/SMTP.pm and not ./SMTP.pm or ./Net::SMTP.pm). >Otherwise, use lib '.' should be your friend. I believe IIS does horribly evil things to the current execution directory. Roger
Re: MSA rewrite project
Jonathan Peterson wrote: > 2. including the required modules as simple .pm files to be > uploaded to the same directory as the script file. (i.e. no > proper 'perl Makefile.PL;make;make test;make install). > > Assuming that 2 actually works, which is should in many but > not all cases. Generally, @INC contains '.', so it should work (though remember that Net::SMTP has to go into ./Net/SMTP.pm and not ./SMTP.pm or ./Net::SMTP.pm). Otherwise, use lib '.' should be your friend. Cheers, Philip -- Philip Newton <[EMAIL PROTECTED]> All opinions are my own, not my employer's. If you're not part of the solution, you're part of the precipitate.
MSA rewrite project
> > Dave Cross wrote: > > I've just seen a downside to the "no non-standard modules" > > rule, which is that we'll have to send all mail by piping > > to sendmail. And that really hits your cross-platform > > compatibility. > > Well, it depends on how much pain you want to inflict on yourself. > Which is a greater evil: 1. writing the code to not require non-standard modules. 2. including the required modules as simple .pm files to be uploaded to the same directory as the script file. (i.e. no proper 'perl Makefile.PL;make;make test;make install). Assuming that 2 actually works, which is should in many but not all cases. I suggest that 2 is the less of two weevils, in those places where it works.
