> Because this uses *my* environment when I run *your* Perl script.
> That's broken.

> Hardcode the path.  Or install it using any of the module tools, which
> will replace #!perl with the proper hardcoded local Perl path.

I also view this as a deployment problem which has probably been solved many 
times by
now.  The other similar but not identical deployment problem revolves around 
@INC.  Both
of these deployment challenges are exaggerated by lack of root privileges on 
linux
boxes.  Can someone recommend any particularly good resources or tools for 
addressing
these issues?

--
Ronald Weidner


**********************************************************************
This e-mail is intended solely for the intended recipient or recipients. If 
this e-mail is addressed to you in error or you otherwise receive this e-mail 
in error, please advise the sender, do not read, print, forward or save this 
e-mail, and promptly delete and destroy all copies of this e-mail. 
This email may contain information that is confidential, proprietary or secret 
and should be treated as confidential by all recipients. This e-mail may also 
be a confidential attorney-client communication, contain attorney work product, 
or otherwise be privileged and exempt from disclosure. If there is a 
confidentiality or non-disclosure agreement or protective order covering any 
information contained in this e-mail, such information shall be treated as 
confidential and subject to restriction on disclosure and use in accordance 
with such agreement or order, and this notice shall constitute identification, 
labeling or marking of such information as confidential, proprietary or secret 
in accordance with such agreement or order.
The term 'this e-mail' includes any and all attachments.
**********************************************************************

Reply via email to