Historical bug tracker for the Pacman package manager.
The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues
This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues
This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
FS#2218 - gtk-doc directory not part of AL philosophy
Attached to Project:
Pacman
Opened by Dusty Phillips (Dusty) - Wednesday, 16 February 2005, 17:37 GMT
Last edited by Judd Vinet (judd) - Wednesday, 16 February 2005, 20:30 GMT
Opened by Dusty Phillips (Dusty) - Wednesday, 16 February 2005, 17:37 GMT
Last edited by Judd Vinet (judd) - Wednesday, 16 February 2005, 20:30 GMT
|
DetailsVarious packages place programmer documentation in the /usr/share/gtk-doc directory. as with info pages, should this info not be stripped from these packages?
Discussion here: http://bbs.archlinux.org/viewtopic.php?t=10021&start=30 |
This task depends upon
The gtk-doc things are API docs that are mainly used by developers. The common user doesn't use them and the API docs don't build on tons of packages (the included gtk-doc shit is old stuff that was pregenerated when the upstream maintainer rolled a release and could be very old documentation because it doesn't build always)
Also, the huge KDE/QT stuff that uses make apidox or whatever that says worries me: Do we need the API DOCs, or could we split it in a -doc package?