manpage not recognized if doesn't start with ".TH "
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-distutils-extra (Ubuntu) |
Fix Released
|
Medium
|
Dominique Lasserre |
Bug Description
I have a manpage that starts with a "Hey, EMACS:" line [0], which is how the example files is created when following the Debian new maintainer's guide.
distutils-extra considers a file that matched '*.[0123456789]' as a valid man page only if it starts with the string ".TH " [1]. This results in that manpage to not be automatically recognized, and has 2 consequences:
- You need to add a line in MANIFEST.in with "include doc/*"
- The file appears in the list printed after "WARNING: the following files are not recognized by DistUtilsExtra.
Maybe the check to see if the file is a valid manpage should do something like this:
if line.startswith
[0] bazaar.
[1] http://
Related branches
- Martin Pitt (community): Needs Fixing
-
Diff: 20 lines (+6/-4)1 file modifiedDistUtilsExtra/auto.py (+6/-4)
affects: | python-distutils-extra → python-distutils-extra (Ubuntu) |
Changed in python-distutils-extra (Ubuntu): | |
status: | In Progress → Fix Committed |
importance: | Undecided → Medium |
gmanedit also adds a comment at the beginning of man pages, to the same effect.
Apparently they can be moved down the file a line without harm (as a circumvention).