Hi,
On 1/17/25 05:14, Sam Hartman wrote:
With the exception of Simon Richter, we appear to be agreed that
avoiding man pages in m-a: same packages is good.
I mean, this is specifically about the manpages included in
libpam-modules, which are at the intersection of
- likely to be useful when the full -doc package is not installed
- in a m-a:same package
- built with a tool that insists on inserting a comment with its own
version number into output files
So generalizing this to a rule to not ship manpages in m-a:same packages
is overly broad -- basically we'd have to give every -dev package
containing manual pages a -doc package, which is not really economical,
especially when it's only a problem for generated manpages, and the
differences between versions of the file are in comment lines.
For libpam-modules itself, because there is a -runtime package already,
moving the manpages there is a good solution, but it's not something I
believe should become a general rule, because there absolutely are use
cases for user facing documentation shipped with library packages.
Simon
