Originally posted by: toojays
When I run a "git svn" command it complains like:
$ git svn info
Can't locate Git.pm in @INC (you may need to install the Git module) (@INC contains: /opt/freeware/share/perl5 /opt/freeware/lib/perl5/site_perl/5.28.1/ppc-aix-thread-multi /opt/freeware/lib/perl5/site_perl/5.28.1 /opt/freeware/lib/perl5/5.28.1/ppc-aix-thread-multi /opt/freeware/lib/perl5/5.28.1 /opt/freeware/lib/perl5/site_perl) at /opt/freeware/lib/perl5/5.28.1/Git/SVN.pm line 17.
BEGIN failed--compilation aborted at /opt/freeware/lib/perl5/5.28.1/Git/SVN.pm line 24.
Compilation failed in require at /opt/freeware/libexec64/git-core/git-svn line 22.
BEGIN failed--compilation aborted at /opt/freeware/libexec64/git-core/git-svn line 22.
The reason is that Git.pm is installed in the man pages directory instead of in the Perl search path:
$ rpm -ql perl-Git | grep Git.pm
/opt/freeware/man/man3/Git.pm
I can get around that with the following symlink:
# ln -s /opt/freeware/man/man3/Git.pm /opt/freeware/lib/perl5/5.28.1/Git.pm
Of course git-svn still doesn't work properly because we don't have a perl-Subversion package, but fixing perl-Git would be progress.
BTW, I'm no perl guru, but I see the perl-Git package installs most of the .pm files in /opt/freeware/lib/perl5/5.28.1. It seems overly restrictive to bind the files to the patchlevel of Perl. Would it be reasonable to install into /opt/freeware/share/perl5 instead?