AMPT0659@s2901b.amp.com (03/13/91)
Hello all!
I know that the question of compiling Perl has come up many
times before but... My client is starting to really LIKE Perl.
They would like to use it for several "system" level utilities and
projects. Unfortunately that have a very small staff (gee, good
thing none of us has that problem :) and they are afraid of the
support aspect of letting Perl fall into the hands of their users.
They would like to:
a). restrict the use of Perl to specific jobs or projects.
b) if possible provide a single 'executable' that would plug and
play for each project. Having a platform specific executable
is acceptable. They just don't want to worry about thinking
"Hmm, what version of Perl is on this system?" or "How do we
update all those copies of Perl?"
Dump has ben mentioned but I am unfamiliar with it. Does
anyone have suggestions. The client expects to have around a
thousand workstations on-line by next year and I can understand
their position from a maintainence point of view.
Thanks in advance for any suggestions. FLAMES > /dev/null
John C. Kelly MaBell: 717-986-5038
Prime System Integration Prime: j.kelly@md-b.prime.com
Prime Computer Inc. Client: ampt0659@s2901b.amp.com
DISCLAIMER: I speak for me. Only. Home: jkelly@world.std.com
"You can demonstrate a program for an executive - but you can't make
him computer literate."