On Fri, 11 Mar 2005, Adam Heath wrote:
> Name: disable-html-docs.patch
> Depends: add-build.patch
> Description: disable html docs, as they use non-free tools.
> Building the html docs requires latex2html, which is non-free. Disabling
> them allows for xen to be uploaded to main.
> This is not a big deal, as ps and pdf forms of the documentation are
> still included.
> Signed-off-by: Adam Heath <doogie@xxxxxxxxxxxxx>
> --- xen-2.0.5.orig/docs/Makefile
> +++ xen-2.0.5/docs/Makefile
> @@ -19,7 +19,7 @@
> GFX = $(patsubst %.fig, %.eps, $(wildcard figs/*.fig))
> all: build
> -build: ps pdf html
> +build: ps pdf
> rm -f *.aux *.dvi *.bbl *.blg *.glo *.idx *.ilg *.log *.ind *.toc
> ps: $(DOC_PS)
> @@ -38,7 +38,6 @@
> $(INSTALL_DIR) $(DESTDIR)$(pkgdocdir)
> cp -dR ps $(DESTDIR)$(pkgdocdir)
> cp -dR pdf $(DESTDIR)$(pkgdocdir)
> - cp -dR html $(DESTDIR)$(pkgdocdir)
> pdf/%.pdf: ps/%.ps
> $(INSTALL_DIR) $(@D)
I see that a variant of this has been applied to 2.0-testing. Unforunately,
just doing "which latext2html" won't suffice, as the package may actually be
installed, but we can't call it.
I can Build-Conflict with it, which will solve the problem, but then those
people who do like using latex2html will dislike me.
I've been thinking of writing a configure script, and this may be the kindling
that starts the fire.
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
Xen-devel mailing list