L
Lax
Hi all,
Could someone give me a clue how the @INC path of a Perl installation
is constructed.
I'd installed a thirdparty package which was shipped with its own
version of Perl. Installing it put the software's bin folder in the
PATH variable first and it overrides any other Perl installation on the
machine.
The @INC path for invocation of any perl .exe from other installations,
always displays the package's bin first. Is there any way I could avoid
that from happening? The package's Perl is incompatible with a few of
my scripts.
I tried changing the system PATH env variable to put the desired Perl
installation bin folder first in the PATH. Even though, the PATH has
changed, the @INC doesnt seem to change.
I dont want to uninstall the software just on this account
Thanks for your time,
Lax
Could someone give me a clue how the @INC path of a Perl installation
is constructed.
I'd installed a thirdparty package which was shipped with its own
version of Perl. Installing it put the software's bin folder in the
PATH variable first and it overrides any other Perl installation on the
machine.
The @INC path for invocation of any perl .exe from other installations,
always displays the package's bin first. Is there any way I could avoid
that from happening? The package's Perl is incompatible with a few of
my scripts.
I tried changing the system PATH env variable to put the desired Perl
installation bin folder first in the PATH. Even though, the PATH has
changed, the @INC doesnt seem to change.
I dont want to uninstall the software just on this account
Thanks for your time,
Lax