Re: Debhelper - docbookxml manpages
On 8/17/07, Sylvain Le Gall <email@example.com> wrote:
> On 17-08-2007, Carl Fürstenberg <firstname.lastname@example.org> wrote:
> > On 8/17/07, Sylvain Le Gall <email@example.com> wrote:
> >> Hello,
> >> I just read your script which is quite interesting. I am working on a
> >> CDBS class for managing docbook-xml generated manpage and po4a
> >> translation of it. For now, it works quite well and i have tested it in
> >> some of my packages. You can have a look at this here:
> >> http://svn.debian.org/wsvn/pkg-ocaml-maint/trunk/packages/cameleon/trunk/debian/mk/docbook-manpage.mk?op=file&rev=0&sc=0
> >> http://svn.debian.org/wsvn/pkg-ocaml-maint/trunk/packages/cameleon/trunk/debian/mk/po4a.mk?op=file&rev=0&sc=0
> >> http://svn.debian.org/wsvn/pkg-ocaml-maint/trunk/packages/cameleon/trunk/debian/rules?op=file&rev=0&sc=0
> >> You can also have a look at other package i do with it: camlidl,
> >> camomile. (same subversion repository, or use debcheckout).
> >> I am maintaining the source of this CDBS class on a private VCS, but i
> >> am willing to collaborate, if you think there is something that you can
> >> reuse for po4a files (speaking for me, i think i will try to copy you
> >> way to guess manpage section ;-).
> >> Regards,
> >> Sylvain Le Gall
> >> --
> >> To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
> >> with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org
> > I made first a cdbs script (see
> > http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=15;filename=docbook-xml-manpage.mk;att=1;bug=433852
> > ), though without po4a support, then I was asked that it should be a
> > debhelper program instead. After that I got feedback that it shouldn't
> > build and install in the same script (from irc).
> OK, now i see that you already know my CDBS class (since you derive you
> first work on it).
> I am really not sure it should be a debhelper script, since it will make
> debhelper depends on docbook-xml... Which is not good in my mind.
> Maybe you could split the thing as this :
> * define a debian/XXX.docbookxmlmanpages file, it contains all
> the toplevel xml file to install (firt column) and the generated manpage
> (optional, second column). If the generated manpage is not defined, it
> is assumed that it will be generated in the same directory of the
> source XML and using the name you can guess out of the XML file (just
> as you do in your debhelper script)
> * the CDBS class will use the debian/*.docbookxmlmanpages as an input to
> guess what file to generate
> * the debhelper script will use the debian/*.docbookxmlmanpages as an
> input to install the generated manpage.
> People who don't want to use the CDBS class, can generate the manpage by
> another way and still use everything (except the CDBS class).
> People who want to use the CDBS class, just have to write the manpage
> If i am missing something, let me know. In particular, i don't have
> followed the IRC talk about this (maybe you can send me a quick
> If you are interested in providing a full support of docbook XML
> manpage, just tell me and i will give you a copy of my DARCS repository
> so we can work on a good solution (before proposing to integrate it into
> Sylvain Le Gall
> Sylvain Le Gall
> To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact email@example.com
A thing to remember is that one xml file can result in multiple man
pages, that's why I'm using libxml to grab all the manpages from the
xml file, in the cdbs version to know what to remove, and in the
debhelper version to know what file to install.
/Carl Fürstenberg <firstname.lastname@example.org>