in reply to Re: Using my version of a cpan module
in thread Using my version of a cpan module

I think the PERL5LIB path is weird since normally it isn't needed - it's in @INC. But OP is using the Git for Windows perl, not Strawberry (C:\Strawberry\Perl\bin\perl.exe) but wants to use the libraries installed in Strawberry with the Git for Windows perl. So he has to configure PERL5LIB with paths that would normally be in @INC, but the Strawberry paths aren't in the Git for Windows perl @INC.

A bit of kludge if you ask me, I just use PowerShell (way more capable than cmd.exe and can be customized to be like bash) so I don't need to use Git for Windows bash and thus never have the perl conflict issue.

  • Comment on Re^2: Using my version of a cpan module

Replies are listed 'Best First'.
Re^3: Using my version of a cpan module
by WPeacock (Initiate) on Jul 19, 2019 at 21:58 UTC
    Actually, when I said "My .bashrc sets $PATH to Strawberry perl" I should have quoted my (now modified per ^2) .bashrc:
    if [ -x /c/Strawberry/perl/bin/perl.exe ] ; then export PATH="/c/Strawberry/perl/bin:/c/Strawberry/c/bin:$PATH" export PERL5LIB=/c/Strawberry/perl/site/lib:/c/Strawberry/perl/vendor +/lib fi

    So, my git bash is really using Strawberry Perl instead of MinGW's Perl that doesn't have CPAN