On Fri, 2003-01-17 at 12:18, Christian Marillat wrote:
> Another good reason to call configure with --disable-gtk-doc. Here is
> what happens when a documentation use xml DTD :
>
> *** Building HTML ***
> test -d ./html || mkdir ./html
> cd ./html && gtkdoc-mkhtml gnome-vfs ../gnome-vfs-docs.sgml
> xmlNanoHTTPConnectAttempt: Connect attempt timed
> out.xmlNanoHTTPConnectAttempt: Connect attempt timed
> out.../gnome-vfs-docs.sgml:43: warning: failed to load external entity
> "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd"; ]>
I understand how the gtk-doc Makefiles work now (the first library I
packaged using gtk-doc was actually broken). The latest policy document
states to use --disable-gtk-doc unless the docs in the tarball are
broken/out-of-date:
<para>
If the upstream tarball contains documentation for a library
which is generated using <application>gtk-doc</application> or
<application>doxygen</application>, it should not be
regenerated during the Debian package build process.
<footnote>
<simpara>In the case of gtk-doc, this means passing the
<varname>--disable-gtk-doc</varname> flag to
<filename>configure</filename>.</simpara>
</footnote>.The only exception to this rule is if the upstream
tarballs contains incomplete or old API documentation.
</para>
In other news, I now have written dh_scrollkeeper too. I'll package
them up in a separate debhelper-gnome package for now.
Ross
--
Ross Burton mail: ross@burtonini.com
jabber: ross@nerdfest.org
www: http://www.burtonini.com./
PGP Fingerprint: 1A21 F5B0 D8D0 CFE3 81D4 E25A 2D09 E447 D0B4 33DF
Attachment:
signature.asc
Description: This is a digitally signed message part