Many packages provide man3 (and other) man pages with generic names. The case in question in ncarg-devel and allegro-devel which both provide man3/line.3.gz. So, what do we do?
- package in /usr/share/<package>/man/? If so, how to we update MANPATH? How does man handle finding both (all) of the man pages?
- rename to something like <package>_<manpage>? Do we always do this? Only if a file conflicts? Is there an easy way to find conflicts before packaging?
- suffixes <manpage>.3<suffix> ? Can man handle this?
Please help!
On Fri, 2006-02-17 at 22:47 -0700, Orion Poplawski wrote:
Many packages provide man3 (and other) man pages with generic names. The case in question in ncarg-devel and allegro-devel which both provide man3/line.3.gz. So, what do we do?
It's ludicrous to package such man pages. If documentation is generated via doxygen you can set MAN_LINKS to NO in Doxyfile in order to suppress them, otherwise just delete them.
Orion Poplawski wrote:
Many packages provide man3 (and other) man pages with generic names. The case in question in ncarg-devel and allegro-devel which both provide man3/line.3.gz. So, what do we do?
- package in /usr/share/<package>/man/? If so, how to we update
MANPATH? How does man handle finding both (all) of the man pages?
IMO, no. It's not worth the extra hassle.
- rename to something like <package>_<manpage>?
+1
Do we always do this? Only if a file conflicts?
Yep.
Is there an easy way to find conflicts before packaging?
Not that I'm aware. It should be rare enough that it can be handled on a case-by-case basis.
- suffixes <manpage>.3<suffix> ? Can man handle this?
Another possibility, but I'm unfamiliar with that convention.
-- Rex
Rex Dieter wrote:
Orion Poplawski wrote:
Many packages provide man3 (and other) man pages with generic names. The case in question in ncarg-devel and allegro-devel which both provide man3/line.3.gz. So, what do we do?
...
- rename to something like <package>_<manpage>?
Do we always do this? Only if a file conflicts?
Yep.
Oops, ambiguous answer. Yep, rename for the latter case (only for conflicts).
-- Rex
On Mon, 2006-02-20 at 06:39 -0600, Rex Dieter wrote:
Orion Poplawski wrote:
Many packages provide man3 (and other) man pages with generic names. The case in question in ncarg-devel and allegro-devel which both provide man3/line.3.gz. So, what do we do?
- rename to something like <package>_<manpage>?
+1
Works for section 3 but not for section 1 (application man packages). There, each man page should match the name of the tool it is trying to describe.
But, if section 1 man pages clash, the apps probably also do.
Is there an easy way to find conflicts before packaging?
Not that I'm aware.
It's close to impossible, because man page conflicts normally occur at installation time, due to parallel installations of alternative implementations (or badly designed packages).
- suffixes <manpage>.3<suffix> ? Can man handle this?
Another possibility, but I'm unfamiliar with that convention.
It's the traditional standard on many non-Linux *nixes.
Unfortunately Linux' "man" doesn't handle these sufficiently well. [Install Inventor-devel and Coin2-devel from FE, if you'd like to experiment with this convention. .3iv vs. .3]
Ralf
Ralf Corsepius wrote:
On Mon, 2006-02-20 at 06:39 -0600, Rex Dieter wrote:
Orion Poplawski wrote:
Is there an easy way to find conflicts before packaging?
Not that I'm aware.
It's close to impossible, because man page conflicts normally occur at installation time, due to parallel installations of alternative implementations (or badly designed packages).
I was hoping for some repoquery magic.... Anyone?
On Mon, 20 Feb 2006, Orion Poplawski wrote:
Ralf Corsepius wrote:
On Mon, 2006-02-20 at 06:39 -0600, Rex Dieter wrote:
Orion Poplawski wrote:
Is there an easy way to find conflicts before packaging?
Not that I'm aware.
It's close to impossible, because man page conflicts normally occur at installation time, due to parallel installations of alternative implementations (or badly designed packages).
I was hoping for some repoquery magic.... Anyone?
Well you can pass a list of files to repoquery to see if they match. Eg something like repoquery -f `rpm -qpd <yourpackage.rpm>`
If you get matches, you have a conflict - or at least a potential conflict.
- Panu -
packaging@lists.fedoraproject.org