about summary refs log tree commit diff
path: root/doc/manual/bugs.xml
diff options
context:
space:
mode:
authorEelco Dolstra <e.dolstra@tudelft.nl>2006-08-21T16·05+0000
committerEelco Dolstra <e.dolstra@tudelft.nl>2006-08-21T16·05+0000
commit1a9a1f2768bac5defe4c2e39e5a9ccdee0e05d55 (patch)
treed3d0269ae4b2392edd5b547215fa527283c70725 /doc/manual/bugs.xml
parentcc0505f033f9d7f55837dca7b3bb4fb3d2969afb (diff)
* Convert to DocBook 5.
* Use Jing for RelaxNG validation, xmllint seems buggy.

Diffstat (limited to 'doc/manual/bugs.xml')
-rw-r--r--doc/manual/bugs.xml17
1 files changed, 11 insertions, 6 deletions
diff --git a/doc/manual/bugs.xml b/doc/manual/bugs.xml
index 9f8faae96ba8..d21603559ddc 100644
--- a/doc/manual/bugs.xml
+++ b/doc/manual/bugs.xml
@@ -1,4 +1,8 @@
-<appendix><title>Bugs / To-Do</title>
+<appendix xmlns="http://docbook.org/ns/docbook"
+          xmlns:xlink="http://www.w3.org/1999/xlink">
+
+<title>Bugs / To-Do</title>
+
 
 <itemizedlist>
 
@@ -15,11 +19,12 @@ implemented; generations form a linear sequence.</para></listitem>
 is already possible to do build management using Nix (by writing
 builders that perform appropriate build steps), but the Nix expression
 language is not yet powerful enough to make this pleasant (?).  The
-language should be extended with features from the <ulink
-url='http://www.cs.uu.nl/~eelco/maak/'>Maak build manager</ulink>.
-Another interesting idea is to write a <command>make</command>
-implementation that uses Nix as a back-end to support <ulink
-url='http://www.research.att.com/~bs/bs_faq.html#legacy'>legacy</ulink>
+language should be extended with features from the <link
+xlink:href='http://www.cs.uu.nl/~eelco/maak/'>Maak build
+manager</link>.  Another interesting idea is to write a
+<command>make</command> implementation that uses Nix as a back-end to
+support <link
+xlink:href='http://www.research.att.com/~bs/bs_faq.html#legacy'>legacy</link>
 build files.</para></listitem>
 
 <listitem><para>For security, <command>nix-push</command> manifests