Bug 117530
Summary: | developer docs not provided in -devel rpm | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | George Karabin <gkarabin> |
Component: | libgnome | Assignee: | Ray Strode [halfline] <rstrode> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | kmaraas |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-05-13 14:41:57 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
George Karabin
2004-03-04 23:24:51 UTC
To follow up, I've come to understand that the presence or absence of the help files depends on how the release tarball was generated. The part of the release process that makes the documentation and installs it in the tarball appears to be manual. Unless the upstream maintainer == fedora maintainer, it seems risky to assume it's always done, given past history. The latest release ships with the html help files and devhelp, but the last one didnt. For consistency, I'd think it would be best to always --enable-gtk-doc in the SRPM spec file configure command. Would be nice to hear why the docs were disabled. Hi, I'm going through bugs assigned to me and attempting to clean some of the older, fixed ones up. This bug hasn't changed in over a year old now. Are you still seeing the problem? (This a batch message is being sent to all my bugs that haven't changed in a year) This has been fixed. The docs are there in fedora core 4 test at least. Thanks Kjartan. I'll close this bug. |