Mailing List Archive

[Bug 5470] spamassassin-run Manpage Dumplicates
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=5470

Henrik Krohns <apache@hege.li> changed:

What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|Undefined |4.0.0
CC| |apache@hege.li

--- Comment #1 from Henrik Krohns <apache@hege.li> ---
Tried looking at this, but I could not figure out how the man3 pages are
generated. :-D

--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 5470] spamassassin-run Manpage Dumplicates [ In reply to ]
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=5470

Bill Cole <billcole@apache.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |billcole@apache.org
Resolution|--- |WONTFIX
Status|NEW |RESOLVED

--- Comment #2 from Bill Cole <billcole@apache.org> ---
(In reply to Henrik Krohns from comment #1)
> Tried looking at this, but I could not figure out how the man3 pages are
> generated. :-D

The man3 pages are generated by the manifypods make target, which is generated
by the default behavior of ExtUtils::MakeMaker. EU::MM finds all .pod files and
.pm files containing POD markup in the source tree, and adds them to the
MAN3PODS list, which it uses (along with MAN1PODS and other macros) to generate
the manifypods target.

I've played around a bit with Makefile.PL, file location, and MANIFEST to try
to keep EU::MM from including spamassassin-run.pod in MAN3PODS with no luck.
Short of completely overriding the automated default value of MAN3PODS (a large
hashref with an item for each *.pm file) I don't see how to include everything
except spamassassin-run.pod.

I'm also not sure we SHOULD. It is normal to have man pages for perl objects in
manual section 3 or 3pm but it is also normal to have the man page for
executables (e.g. the spamassassin script, which spamassassin-run.pod
documents) in section 1/1pm. This is arguably as much a feature as it is a bug.

--
You are receiving this mail because:
You are the assignee for the bug.