Jari Aalto wrote: > 1. This feature would really simplify maintaining manual pages.
It avoids 2 lines in the rules file (a call to pod2man and passing dh_clean the generated file.) > 2. there are fair number of packages whose upstream is not (for various > reasons) shipping manual pages. > > 3. Taking gover maintenance of a Debian package that contains raw > debain/*.1 manual pages is not really comfortable. The best format to write such man pages in is the format most likely to be accepted by upstream. Which varies enormously amoung packages. > Debhelper could simply provide defaults and read further information > embedded from *.pod files. something like this: But this is nonstandard, so now anyone familiar with POD but not with this extension won't understand it, and there is no nice simple pod2man command line being developed that can be passed to upstream along with the pod files. Instead there is Debian-specific magic, which actively discourages getting the man pages upstream. I really appreciate you taking the time to write patches, but I wish you'd listened to the reasons I gave for closing the bug first. Your patch expands dh_installman's code size by 30%, and expands the size of its man page by 50%. If I add this to dh_installman, I'd expect people will next want it to support docbook2man and all sorts of other things, and I cannot accept that bloat. And so I have to say that generating man pages is out of scope for dh_installman, as the "install" in its name might suggest, and leave it at that. -- see shy jo
signature.asc
Description: Digital signature
