Anton Aylward wrote:
Yes you are right when you point out that the tools that build the the MAN index db come with the package. But those tools make use of what is in /etc/manpath.config. If a user adds new stuff ... ~/mydevelopmentsprojects/man ... then that needs to be added so that it gets indexed. Not different with perl documentation. By default MAN91) wants things in man/troff format, so ether convert, or supply the information to convert-on-the-fly using pos2man.
MAN91 should also recognize things in cat
I don't want to have different things for different apps, I want consistency. I want 'apropos' and 'man' to work with everything.
---- AFAIK, they do.
Please note, that the cognitive load even of that example when dealing with "Mail::SpamAssassin" needs to the modules group -- "Mail" and that module name is in CamelCase. Compare with the simplicity of the MAN(1) version.
I agree w/that!... but note: having "man" ignore case is a suse 'extension' that isn't on every platform.
Ah, and while 'man pod2man' returned nothing,
Then you do not have perl-doc 5.16 nor 5.18 installed: rpm -ql perl-doc|grep pod2man /usr/share/man/man1/pod2man.1.gz
Then when 'mkwhatis' runs tonight, it will get indexed and 'man pod2man' will now work.
Wouldn't just installing the perl-doc package be better?
Of course I can also run "file /usr/bin/* | grep 'Perl script'" to see what else is there and see what else doesn't already have a MAN page. Although since not every perl script will have embedded POD, perhaps this is a better way of finding those that do and are candidates for 'pod2man':
grep -l "=head1" /usr/bin/*
---- Most should have their own man page... If they don't, it's likely a bug or oversight. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org