Bug 845946 - libtevent owns the system level manpage directory and does not build man pages
Summary: libtevent owns the system level manpage directory and does not build man pages
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: libtevent
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Simo Sorce
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-08-06 08:14 UTC by Jakub Hrozek
Modified: 2012-08-17 13:44 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-08-17 13:44:10 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
a spec file patch. (1.86 KB, patch)
2012-08-06 08:14 UTC, Jakub Hrozek
sgallagh: review+
Details | Diff

Description Jakub Hrozek 2012-08-06 08:14:18 UTC
Created attachment 602457 [details]
a spec file patch.

Description of problem:
libtevent in rawhide seems to be owning the top-level directory for man page section 3:

%{_mandir}/man3/

It also doesn't build man pages, because it lacks the proper BuildRequries. 

Including the man pages might be questionable because the same information is mostly included in the header file and completely included in the upstream HTML documentation.

Version-Release number of selected component (if applicable):
0.9.16-2

How reproducible:
specfile inspection, rpmlint

Additional info:
a patch is attached. Andreas already fixed the issue with exclude patterns in tevent upstream.

Comment 1 Stephen Gallagher 2012-08-06 11:57:21 UTC
Comment on attachment 602457 [details]
a spec file patch.

The patch looks good. Despite the upstream documentation being good, I'd still prefer to have the manpages included in the package simply because this way they are viewable while disconnected. The comments in the header file are good, but somewhat less easily-readable.

Comment 2 Jakub Hrozek 2012-08-17 13:44:10 UTC
Fixed in libtevent-0.9.16-3


Note You need to log in before you can comment on or make changes to this bug.