At 09:19 AM 12/15/97 +1100, Alex Satrapa wrote: >At 05:52 +1100 on 15/12/97, Jon S. Jaques wrote: >>What is the best way to distribute MacPerl across a LAN without installing >>MacPerl on each Mac client? >That's the way I do it. MacPerl, unlike most Windows or Microsoft programs, >is entirely self-contained - all the stuff you need to run MacPerl is in >one folder. Wherever that folder is, your (default) libs go too. That's how >The only thing to be wary of is custom libs - there is a "MacPerl <version >#> Preferences" file in System:Preferences. My guess is this contains stuff >like custom library paths. The only effect this would have (AFAIK) is if OK, that should do it... I'm not currently using any custom libs, but I think that if I did end up requiring it, I'd just drop them into the default lib folder. Does it affect the performance of the script by having the executables on a network drive? >Windows 95: n. 32 bit extensions and a graphical shell for a 16 bit patch >to an 8 bit operating system originally coded for a 4 bit microprocessor, >written by a 2 bit company that can't stand 1 bit of competition. -- OS8~Win95 -- Jon S. Jaques -- The Grove Hill Pages -- -- Now on the PerlRing! -- -- http://www.grovehillsys.com/scripting -- -- jjaques@grovehillsys.com -- -- Linux: Salvation from Bill, Steve and Marc! -- ***** Want to unsubscribe from this list? ***** Send mail with body "unsubscribe" to mac-perl-request@iis.ee.ethz.ch