Giovanni Scafora a écrit : > 2009/10/8, Firmicus <Firmicus@xxxxxxx>: > >> See http://bugs.archlinux.org/task/16488 >> >> But please, "broken" is too strong! Perl is not broken. It's just that >> because of the purge options in makepkg.conf, all pods have been >> deleted. But ALL the documentation is still there in the form of manpages. >> > > Hi Firmicus, > > I guess that you should fix this issue about all pods. > Please, see the following lines: > > ff0000@regulus:~$ perl -Mdiagnostics -e 'exit 0' > couldn't find diagnostic data in > /usr/share/perl5/core_perl/pods/perldiag.pod > /usr/lib/perl5/site_perl/5.10.1 /usr/share/perl5/site_perl/5.10.1 > /usr/lib/perl5/vendor_perl /usr/share/perl5/vendor_perl > /usr/share/perl5/vendor_perl /usr/lib/perl5/core_perl > /usr/share/perl5/core_perl /usr/lib/perl5/current > /usr/lib/perl5/site_perl/current . -e at > /usr/share/perl5/core_perl/diagnostics.pm line 268, <POD_DIAG> line > 647. > Compilation failed in require, <POD_DIAG> line 647. > BEGIN failed--compilation aborted, <POD_DIAG> line 647. > > Yes this is one is a special case where a module needs a pod file. As you can read on Flyspray I am currently preparing a fixed release with the option '!purge'. But I will still manually delete all podfiles EXCEPT those in /usr/share/perl5/core_perl/pods/. For the rest, manpages are there. Btw I was not aware that pod files were now being removed automatically. This was not the case in the past! F
