Don't require your users to set PERL5LIB themselves in order to run your scripts. Set it yourself (locally for the process), in a wrapper script, or some such. If they then still insist on pointing their PERL5LIB to your private libs in their day-to-day environment, it's their problem...
You could also write the wrapper such that it copies the contents of some other env variable (e.g. XX_ROOT) into PERL5LIB. This way, they could make their choice by setting XX_ROOT without affecting anthing else, while you can still take advantage of PERL5LIB, to avoid littering use lib all over the place.
#!/bin/sh export PERL5LIB=$XX_ROOT exec ...
P.S.: Perl's -I command line option could be used similarly:
#!/bin/sh exec perl -I$XX_ROOT ...
(you can only specify one directory per -I option, though)
In reply to Re^5: layout/configuration of deployed files
by Eliya
in thread layout/configuration of deployed files
by klassa
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |