(sry for the PM by accident) Am Donnerstag, den 16.08.2007, 18:54 +0200 schrieb Carl Fürstenberg: > Per http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=433852#20 I have > made a debhelper script. Though as I have made it, I have some > questions (see attached file): > > 1. should it go into debhelper, or should it be distributed in a new package?
Depends, because you need to depend on docbook-xml, docbook-xsl and xsltproc. Would it be acceptable for debhelper to depend on these packages? > 2. how should language specific things be implemented, for example po4a. For what? I18N of DocBook XML? > 3.is the xmllint invocation needed? it will require that the xml file > are 100% correct, but are that 100% necissary? xsltproc will not need xmllint. It automatically checks the validity and it will fail with error code 6 (following upstream docs). Because both xsltproc/docbook-xsl and docbook2x > 4. is dh_installmandocbookxml a too long name for the file? I guess so. What about e.g. dh_installmandbxml? Or what about extending dh_installman to also accept XML files in package.manpages, so users don't need several scripts for almost the same stuff. However, this would need to add dependencies to debhelper. FYI: In the bug report I saw your make-snippet. Some time ago I started something similar (I was thinking about putting it into docbook-xsl or creating a new package). Maybe we could compare our results and ideas? I would really like to see a solution in Debian (as make-snippet or Perl script) to handle manpage XML sources. So are you interested? Unfortunately I didn't yet find the time to extend dh_installman (what I was thinking about). I've uploaded my stuff to http://debian.wgdd.de/temp/dbxsl/ (a manpage is there too and the debian-dir shows the usage :)) Maybe it's useful for you too. Please don't hesitate to contact me, if you have questions. I will check your script ASAP, but it will need some days, because I'm very busy up to the middle of september. Regards, Daniel