Red Hat Bugzilla – Bug 140917
lperl-libwww-perl: pod should be marked as %doc (+other spec tweaks)
Last modified: 2007-11-30 17:10:55 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5)
Description of problem:
here is the changelog entry from my spec patch:
- "fixed" group (playing by the rules, "Applications/CPAN" is NOT valid)
- switched Requirements to perl modules, not package names
- updated Requirements versions
- dropped external requires filter (hooked it inside spec)
- dropped BuildRequires: perl (it's already required by rpm-build)
- dropped useless bits
- optional make test
- enhanced files removal procedure
- dropped empty directories
- enhanced files list build procedure: claim every non-system-owned
file/directory, mark every POD file as documentation etc
Version-Release number of selected component (if applicable):
Steps to Reproduce:
rpm -qil perl-libwww-perl
Created attachment 107481 [details]
Created attachment 107482 [details]
spec diff (fixed)
sorry about the previous one, i seem to have reverted at some point the Group
We are moving away from filelists and basing all perl module specs on the spec
I think marking *.pod as %doc, at least when they're installed below one of the
perl install dirs, would be useful.
rpm --showrc | grep -P 'perl_\w+(arch|lib)'
But doing that in each and every perl-* specfile is not so cool; it'd be better
to enhance rpmbuild to take care of that automagically.
Can we close this ticket? The latest version of perl-libwww-perl already
corrects most of the issues reported in comment #1 (the pod files being the big
See also #150363.
REOPEN if Marius is not satisfied.
it's ok to close it... it's too weary to treat POD files as documentation from
the spec, IMHO this should be accounted by rpm itself (same way as it does with
It's slightly more difficult for *.pod than for man pages, which is why I
guess it hasn't been done yet. rpm has stuff in place for marking everything
below a dir as %doc (such as is done for /usr/share/doc, /usr/share/man, ...),
but *.pod are scattered around the perl install dirs meaning the same approach
cannot be used.