Bug 178744
Summary: | Man page name is ridiculous | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Paul Nasrat <nobody+pnasrat> |
Component: | xorg-x11-drv-mouse | Assignee: | X/OpenGL Maintenance List <xgl-maint> |
Status: | CLOSED RAWHIDE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | nalin |
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: | 2006-02-02 08:48:09 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: | |||
Bug Depends On: | |||
Bug Blocks: | 150221 |
Description
Paul Nasrat
2006-01-23 22:40:15 UTC
Currently X.org installs manpages in the same directories as system manpages, causing a conflict of the mouse manpage. All of the X driver manpages have the same manpage name as the driver, which is sensible and consistent. The combination of these two factors, leaves us with a conflicting manpage name. The X.Org manpage has temporarily been renamed in the above manner intentionally as a reminder to fix the underlying and more important issue, which is that of the manpages being installed in the wrong directory intentionally by X.Org upstream. The underlying issue is something that needs to be resolved upstream, and we will be working with upstream to come to a solution, at which point the problem being reported will vanish as we undo this workaround. Adding to FC5Target Perhaps moving this one to section 4x (see xorg-x11-drv-citron, xorg-x11-drv-jamstudio, etc.) where other input driver man pages currently live? All of the X11R7 manpages reside in the system manpage directories. There is no 4x dirs in X11R7. I've renamed the manpage to "mouse-driver" for now, which should be more than adequate workaround for this non-critical problem, until we can get the larger problem addressed upstream, which may or may not be before FC5, however it isn't a major showstopper. The new driver package will be built tonight, but might not hit rawhide until the day after tomorrow. Setting status to RAWHIDE. |