Charles Lane <[EMAIL PROTECTED]> wrote:
|
| How about this as an alternative for finding VMSPIPE.COM:
|
| translate logical PERL_VMSPIPE_DURING_MAKE in LNM$PROCESS,
| and if present, use it.
| else look for a readable PERL_ROOT:[000000]VMSPIPE.COM, if found use it.
| ...otherwise, just fail with a suitable message.
What would you think of this alternative?
1. Search @INC for file.
2. On failure, try dirname($^X).
3. Perhaps as last resort, try Perl_Root:[000000], though I'm
not sure this'll add much.
4. Do the lookup from init_os_extras() (after -I and PERL5LIB
processing, but before the Perl code has a chance to fuss
with @INC or $^X.
Putative advantages: Incorporates normal Perl library mechanisms for
adapting to multiple versions/architecures, and provides a relatively
clean way to redirect. Putative disadvantages: Possible security concern
with -I, but if you allow users to specify -I when invoking sensitive scripts,
you may have a bigger problems (though script can say C<@INC = qw( ... )>);
possible inadvertent breakage through existence of an unrelated vmspipe.com
in -Id directory, as with any Perl library file.
| You test for PERL_VMSPIPE_DURING_MAKE first, since there may be a
If we do decide to go with a logical, let's make it as flexible as
possible, say PERL_UTILS_DIR or somesuch, and translate it as one of the
"secure logicals", especially if it's at the head of the list.
Regards,
Charles Bailey [EMAIL PROTECTED]
