When opening a perl file with app-vim/perl-support-4.9 installed, I receive the following error: Can't locate Perl/Tags.pm in @INC (@INC contains: /etc/perl /home/dan/.gentoo/usr/lib/perl5/site_perl/5.12.3/i686-linux /home/dan/.gentoo/usr/lib/perl5/site_perl/5.12.3 /home/dan/.gentoo/usr/lib/perl5/vendor_perl/5.12.3/i686-linux /home/dan/.gentoo/usr/lib/perl5/vendor_perl/5.12.3 /home/dan/.gentoo/usr/lib/perl5/site_perl /home/da n/.gentoo/usr/lib/perl5/vendor_perl/5.12.2/i686-linux /home/dan/.gentoo/usr/lib/perl5/vendor_perl/5.12.2 /home/dan/.gentoo/usr/lib/perl5/vendor_perl/5.12.1/i686-linux /home/dan/.gentoo/usr/lib/perl5/vendor_perl/5.12.1 /home/dan/.gentoo/usr/lib/perl5/vendor_perl /home/dan/.gentoo/usr/lib/perl5/5.12.3/i686-linux /home/dan/.gentoo/us r/lib/perl5/5.12.3 /usr/local/lib/site_perl .) at (eval 9) line 1. BEGIN failed--compilation aborted at (eval 9) line 1. Can't call method "process" on an undefined value at (eval 10) line 5. Press ENTER or type command to continue And when saving files: Can't call method "process" on an undefined value at (eval 11) line 5. Press ENTER or type command to continue Installing Perl::Tags with g-cpan resolves these problems.
This bug is still prevalent in 4.10, and that "Can't call method on an undefined value" thing is still a constant pain in the neck. I've added Perl::Tags to the perl-experimental overlay ( http://git.overlays.gentoo.org/gitweb/?p=proj/perl-overlay.git;a=commit;h=4e2a7bebfe44324fbb3d6c9057569e21441d03f2 ) and it solves my problems. perl herd really should be added here and Perl::Tags ( and a dependency Module::Locate ) should probably be added to the main tree as a dependency. Its not a Gentoo Prefix/Alt specific problem.
Perl-Tags and Module-Locate were added to ::gentoo. Thanks
Fixed in 4.11 now in CVS. Note that ~ppc and ~sparc keywords were dropped pending bug #364443.
Thanks for fixing in v4.11. Still a problem in v4.9 & v4.10 though. Haven't tested v4.8 yet.
(In reply to comment #4) > Thanks for fixing in v4.11. Still a problem in v4.9 & v4.10 though. Haven't > tested v4.8 yet. Note that keywords had to be dropped due to the new rdeps so I didn't want to drop keywords on old versions that were just going to be removed soon from the tree. Anyway, I just tossed both versions from the tree so you shouldn't have anything to complain about. :) In terms of 4.8 not working, just use >=4.11 for now and it'll get stabilized once the dropped keywords are re-added.