2016-04-27 14:29:33 +02:00
|
|
|
{ pkgs, options, config, version, revision, extraSources ? [] }:
|
2008-06-05 17:33:17 +02:00
|
|
|
|
2014-08-09 16:30:44 +02:00
|
|
|
with pkgs;
|
2013-10-17 14:09:05 +02:00
|
|
|
|
2011-09-14 20:20:50 +02:00
|
|
|
let
|
2016-07-28 04:27:39 +02:00
|
|
|
lib = pkgs.lib;
|
2009-10-06 01:15:06 +02:00
|
|
|
|
2013-10-23 19:32:19 +02:00
|
|
|
# Remove invisible and internal options.
|
2016-07-28 04:27:39 +02:00
|
|
|
optionsList = lib.filter (opt: opt.visible && !opt.internal) (lib.optionAttrSetToDocList options);
|
2014-08-27 11:53:08 +02:00
|
|
|
|
|
|
|
# Replace functions by the string <function>
|
|
|
|
substFunction = x:
|
2016-07-28 04:27:39 +02:00
|
|
|
if builtins.isAttrs x then lib.mapAttrs (name: substFunction) x
|
2014-08-27 11:53:08 +02:00
|
|
|
else if builtins.isList x then map substFunction x
|
|
|
|
else if builtins.isFunction x then "<function>"
|
|
|
|
else x;
|
2013-10-23 19:32:19 +02:00
|
|
|
|
|
|
|
# Clean up declaration sites to not refer to the NixOS source tree.
|
2016-07-28 04:27:39 +02:00
|
|
|
optionsList' = lib.flip map optionsList (opt: opt // {
|
2016-01-29 16:20:22 +01:00
|
|
|
declarations = map stripAnyPrefixes opt.declarations;
|
2014-08-27 11:53:08 +02:00
|
|
|
}
|
2016-07-28 04:27:39 +02:00
|
|
|
// lib.optionalAttrs (opt ? example) { example = substFunction opt.example; }
|
|
|
|
// lib.optionalAttrs (opt ? default) { default = substFunction opt.default; }
|
|
|
|
// lib.optionalAttrs (opt ? type) { type = substFunction opt.type; });
|
2013-10-23 19:32:19 +02:00
|
|
|
|
2016-01-22 20:22:12 +01:00
|
|
|
# We need to strip references to /nix/store/* from options,
|
|
|
|
# including any `extraSources` if some modules came from elsewhere,
|
|
|
|
# or else the build will fail.
|
|
|
|
#
|
|
|
|
# E.g. if some `options` came from modules in ${pkgs.customModules}/nix,
|
2016-01-29 16:20:22 +01:00
|
|
|
# you'd need to include `extraSources = [ pkgs.customModules ]`
|
2016-01-29 19:34:00 +01:00
|
|
|
prefixesToStrip = map (p: "${toString p}/") ([ ../../.. ] ++ extraSources);
|
2016-07-28 04:27:39 +02:00
|
|
|
stripAnyPrefixes = lib.flip (lib.fold lib.removePrefix) prefixesToStrip;
|
2013-10-23 19:32:19 +02:00
|
|
|
|
2015-09-24 11:47:00 +02:00
|
|
|
# Convert the list of options into an XML file.
|
|
|
|
optionsXML = builtins.toFile "options.xml" (builtins.toXML optionsList');
|
2008-01-04 15:24:42 +01:00
|
|
|
|
2014-08-09 16:30:44 +02:00
|
|
|
optionsDocBook = runCommand "options-db.xml" {} ''
|
2014-11-17 13:41:18 +01:00
|
|
|
optionsXML=${optionsXML}
|
2014-08-27 11:53:08 +02:00
|
|
|
if grep /nixpkgs/nixos/modules $optionsXML; then
|
2013-10-23 20:06:17 +02:00
|
|
|
echo "The manual appears to depend on the location of Nixpkgs, which is bad"
|
|
|
|
echo "since this prevents sharing via the NixOS channel. This is typically"
|
|
|
|
echo "caused by an option default that refers to a relative path (see above"
|
|
|
|
echo "for hints about the offending path)."
|
|
|
|
exit 1
|
|
|
|
fi
|
2015-10-05 13:23:01 +02:00
|
|
|
${libxslt.bin}/bin/xsltproc \
|
2009-10-06 01:47:50 +02:00
|
|
|
--stringparam revision '${revision}' \
|
2014-08-27 11:53:08 +02:00
|
|
|
-o $out ${./options-to-docbook.xsl} $optionsXML
|
2008-01-04 15:24:42 +01:00
|
|
|
'';
|
2009-09-18 17:10:37 +02:00
|
|
|
|
2016-07-28 04:27:39 +02:00
|
|
|
sources = lib.sourceFilesBySuffices ./. [".xml"];
|
2014-08-25 14:33:17 +02:00
|
|
|
|
2016-04-27 14:29:33 +02:00
|
|
|
modulesDoc = builtins.toFile "modules.xml" ''
|
|
|
|
<section xmlns:xi="http://www.w3.org/2001/XInclude" id="modules">
|
|
|
|
${(lib.concatMapStrings (path: ''
|
|
|
|
<xi:include href="${path}" />
|
|
|
|
'') (lib.catAttrs "value" config.meta.doc))}
|
|
|
|
</section>
|
|
|
|
'';
|
|
|
|
|
2014-08-25 14:33:17 +02:00
|
|
|
copySources =
|
|
|
|
''
|
|
|
|
cp -prd $sources/* . # */
|
2014-08-27 12:24:10 +02:00
|
|
|
chmod -R u+w .
|
2016-04-27 14:29:33 +02:00
|
|
|
ln -s ${modulesDoc} configuration/modules.xml
|
2014-08-25 14:33:17 +02:00
|
|
|
ln -s ${optionsDocBook} options-db.xml
|
2017-06-28 17:42:14 +02:00
|
|
|
printf "%s" "${version}" > version
|
2014-08-25 14:33:17 +02:00
|
|
|
'';
|
|
|
|
|
2015-07-22 16:09:00 +02:00
|
|
|
toc = builtins.toFile "toc.xml"
|
|
|
|
''
|
|
|
|
<toc role="chunk-toc">
|
|
|
|
<d:tocentry xmlns:d="http://docbook.org/ns/docbook" linkend="book-nixos-manual"><?dbhtml filename="index.html"?>
|
2015-07-22 16:17:06 +02:00
|
|
|
<d:tocentry linkend="ch-options"><?dbhtml filename="options.html"?></d:tocentry>
|
|
|
|
<d:tocentry linkend="ch-release-notes"><?dbhtml filename="release-notes.html"?></d:tocentry>
|
2015-07-22 16:09:00 +02:00
|
|
|
</d:tocentry>
|
|
|
|
</toc>
|
|
|
|
'';
|
|
|
|
|
nixos/doc: Allow refs from options to the manual
My first attempt to do this was to just use a conditional <refsection/>
in order to not create exact references in the manpage but create the
reference in the HTML manual, as suggested by @edolstra on IRC.
Later I went on to use <olink/> to reference sections of the manual, but
in order to do that, we need to overhaul how we generate the manual and
manpages.
So, that's where we are now:
There is a new derivation called "manual-olinkdb", which is the olinkdb
for the HTML manual, which in turn creates the olinkdb.xml file and the
manual.db. The former contains the targetdoc references and the latter
the specific targetptr elements.
The reason why I included the olinkdb.xml verbatim is that first of all
the DTD is dependent on the Docbook XSL sources and the references
within the olinkdb.xml entities are relative to the current directory.
So using a store path for that would end up searching for the manual.db
directly in /nix/store/manual.db.
Unfortunately, the <olinks/> that end up in the output file are
relative, so for example if you're clicking on one of these within the
PDF, the URL is searched in the current directory.
However, the sections from the olink's text are still valid, so we could
use an alternative URL for that in the future.
The manual doesn't contain any links, so even referencing the relative
URL shouldn't do any harm.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Cc: @edolstra
2016-04-11 18:29:00 +02:00
|
|
|
manualXsltprocOptions = toString [
|
|
|
|
"--param section.autolabel 1"
|
|
|
|
"--param section.label.includes.component.label 1"
|
|
|
|
"--stringparam html.stylesheet style.css"
|
|
|
|
"--param xref.with.number.and.title 1"
|
|
|
|
"--param toc.section.depth 3"
|
|
|
|
"--stringparam admon.style ''"
|
|
|
|
"--stringparam callout.graphics.extension .gif"
|
|
|
|
"--stringparam current.docid manual"
|
|
|
|
"--param chunk.section.depth 0"
|
|
|
|
"--param chunk.first.sections 1"
|
|
|
|
"--param use.id.as.filename 1"
|
|
|
|
"--stringparam generate.toc 'book toc appendix toc'"
|
|
|
|
"--stringparam chunk.toc ${toc}"
|
|
|
|
];
|
|
|
|
|
2017-06-28 19:02:33 +02:00
|
|
|
manual-combined = runCommand "nixos-manual-combined"
|
2016-09-27 15:26:37 +02:00
|
|
|
{ inherit sources;
|
|
|
|
buildInputs = [ libxml2 libxslt ];
|
2017-06-28 19:02:33 +02:00
|
|
|
meta.description = "The NixOS manual as plain docbook XML";
|
2016-09-27 15:26:37 +02:00
|
|
|
}
|
|
|
|
''
|
nixos/doc: Allow refs from options to the manual
My first attempt to do this was to just use a conditional <refsection/>
in order to not create exact references in the manpage but create the
reference in the HTML manual, as suggested by @edolstra on IRC.
Later I went on to use <olink/> to reference sections of the manual, but
in order to do that, we need to overhaul how we generate the manual and
manpages.
So, that's where we are now:
There is a new derivation called "manual-olinkdb", which is the olinkdb
for the HTML manual, which in turn creates the olinkdb.xml file and the
manual.db. The former contains the targetdoc references and the latter
the specific targetptr elements.
The reason why I included the olinkdb.xml verbatim is that first of all
the DTD is dependent on the Docbook XSL sources and the references
within the olinkdb.xml entities are relative to the current directory.
So using a store path for that would end up searching for the manual.db
directly in /nix/store/manual.db.
Unfortunately, the <olinks/> that end up in the output file are
relative, so for example if you're clicking on one of these within the
PDF, the URL is searched in the current directory.
However, the sections from the olink's text are still valid, so we could
use an alternative URL for that in the future.
The manual doesn't contain any links, so even referencing the relative
URL shouldn't do any harm.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Cc: @edolstra
2016-04-11 18:29:00 +02:00
|
|
|
${copySources}
|
|
|
|
|
2017-06-28 19:02:33 +02:00
|
|
|
xmllint --xinclude --output ./manual-combined.xml ./manual.xml
|
|
|
|
xmllint --xinclude --noxincludenode \
|
|
|
|
--output ./man-pages-combined.xml ./man-pages.xml
|
|
|
|
|
|
|
|
xmllint --debug --noout --nonet \
|
|
|
|
--relaxng ${docbook5}/xml/rng/docbook/docbook.rng \
|
|
|
|
manual-combined.xml
|
|
|
|
xmllint --debug --noout --nonet \
|
|
|
|
--relaxng ${docbook5}/xml/rng/docbook/docbook.rng \
|
|
|
|
man-pages-combined.xml
|
|
|
|
|
|
|
|
|
|
|
|
mkdir $out
|
|
|
|
cp manual-combined.xml $out/
|
|
|
|
cp man-pages-combined.xml $out/
|
|
|
|
'';
|
|
|
|
|
|
|
|
olinkDB = runCommand "manual-olinkdb"
|
|
|
|
{ inherit sources;
|
|
|
|
buildInputs = [ libxml2 libxslt ];
|
|
|
|
}
|
|
|
|
''
|
nixos/doc: Allow refs from options to the manual
My first attempt to do this was to just use a conditional <refsection/>
in order to not create exact references in the manpage but create the
reference in the HTML manual, as suggested by @edolstra on IRC.
Later I went on to use <olink/> to reference sections of the manual, but
in order to do that, we need to overhaul how we generate the manual and
manpages.
So, that's where we are now:
There is a new derivation called "manual-olinkdb", which is the olinkdb
for the HTML manual, which in turn creates the olinkdb.xml file and the
manual.db. The former contains the targetdoc references and the latter
the specific targetptr elements.
The reason why I included the olinkdb.xml verbatim is that first of all
the DTD is dependent on the Docbook XSL sources and the references
within the olinkdb.xml entities are relative to the current directory.
So using a store path for that would end up searching for the manual.db
directly in /nix/store/manual.db.
Unfortunately, the <olinks/> that end up in the output file are
relative, so for example if you're clicking on one of these within the
PDF, the URL is searched in the current directory.
However, the sections from the olink's text are still valid, so we could
use an alternative URL for that in the future.
The manual doesn't contain any links, so even referencing the relative
URL shouldn't do any harm.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Cc: @edolstra
2016-04-11 18:29:00 +02:00
|
|
|
xsltproc \
|
|
|
|
${manualXsltprocOptions} \
|
|
|
|
--stringparam collect.xref.targets only \
|
|
|
|
--stringparam targets.filename "$out/manual.db" \
|
2017-06-28 19:02:33 +02:00
|
|
|
--nonet \
|
nixos/doc: Allow refs from options to the manual
My first attempt to do this was to just use a conditional <refsection/>
in order to not create exact references in the manpage but create the
reference in the HTML manual, as suggested by @edolstra on IRC.
Later I went on to use <olink/> to reference sections of the manual, but
in order to do that, we need to overhaul how we generate the manual and
manpages.
So, that's where we are now:
There is a new derivation called "manual-olinkdb", which is the olinkdb
for the HTML manual, which in turn creates the olinkdb.xml file and the
manual.db. The former contains the targetdoc references and the latter
the specific targetptr elements.
The reason why I included the olinkdb.xml verbatim is that first of all
the DTD is dependent on the Docbook XSL sources and the references
within the olinkdb.xml entities are relative to the current directory.
So using a store path for that would end up searching for the manual.db
directly in /nix/store/manual.db.
Unfortunately, the <olinks/> that end up in the output file are
relative, so for example if you're clicking on one of these within the
PDF, the URL is searched in the current directory.
However, the sections from the olink's text are still valid, so we could
use an alternative URL for that in the future.
The manual doesn't contain any links, so even referencing the relative
URL shouldn't do any harm.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Cc: @edolstra
2016-04-11 18:29:00 +02:00
|
|
|
${docbook5_xsl}/xml/xsl/docbook/xhtml/chunktoc.xsl \
|
2017-06-28 19:02:33 +02:00
|
|
|
${manual-combined}/manual-combined.xml
|
nixos/doc: Allow refs from options to the manual
My first attempt to do this was to just use a conditional <refsection/>
in order to not create exact references in the manpage but create the
reference in the HTML manual, as suggested by @edolstra on IRC.
Later I went on to use <olink/> to reference sections of the manual, but
in order to do that, we need to overhaul how we generate the manual and
manpages.
So, that's where we are now:
There is a new derivation called "manual-olinkdb", which is the olinkdb
for the HTML manual, which in turn creates the olinkdb.xml file and the
manual.db. The former contains the targetdoc references and the latter
the specific targetptr elements.
The reason why I included the olinkdb.xml verbatim is that first of all
the DTD is dependent on the Docbook XSL sources and the references
within the olinkdb.xml entities are relative to the current directory.
So using a store path for that would end up searching for the manual.db
directly in /nix/store/manual.db.
Unfortunately, the <olinks/> that end up in the output file are
relative, so for example if you're clicking on one of these within the
PDF, the URL is searched in the current directory.
However, the sections from the olink's text are still valid, so we could
use an alternative URL for that in the future.
The manual doesn't contain any links, so even referencing the relative
URL shouldn't do any harm.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Cc: @edolstra
2016-04-11 18:29:00 +02:00
|
|
|
|
|
|
|
cat > "$out/olinkdb.xml" <<EOF
|
|
|
|
<?xml version="1.0" encoding="utf-8"?>
|
|
|
|
<!DOCTYPE targetset SYSTEM
|
|
|
|
"file://${docbook5_xsl}/xml/xsl/docbook/common/targetdatabase.dtd" [
|
|
|
|
<!ENTITY manualtargets SYSTEM "file://$out/manual.db">
|
|
|
|
]>
|
|
|
|
<targetset>
|
|
|
|
<targetsetinfo>
|
|
|
|
Allows for cross-referencing olinks between the manpages
|
2016-07-28 18:32:56 +02:00
|
|
|
and manual.
|
nixos/doc: Allow refs from options to the manual
My first attempt to do this was to just use a conditional <refsection/>
in order to not create exact references in the manpage but create the
reference in the HTML manual, as suggested by @edolstra on IRC.
Later I went on to use <olink/> to reference sections of the manual, but
in order to do that, we need to overhaul how we generate the manual and
manpages.
So, that's where we are now:
There is a new derivation called "manual-olinkdb", which is the olinkdb
for the HTML manual, which in turn creates the olinkdb.xml file and the
manual.db. The former contains the targetdoc references and the latter
the specific targetptr elements.
The reason why I included the olinkdb.xml verbatim is that first of all
the DTD is dependent on the Docbook XSL sources and the references
within the olinkdb.xml entities are relative to the current directory.
So using a store path for that would end up searching for the manual.db
directly in /nix/store/manual.db.
Unfortunately, the <olinks/> that end up in the output file are
relative, so for example if you're clicking on one of these within the
PDF, the URL is searched in the current directory.
However, the sections from the olink's text are still valid, so we could
use an alternative URL for that in the future.
The manual doesn't contain any links, so even referencing the relative
URL shouldn't do any harm.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Cc: @edolstra
2016-04-11 18:29:00 +02:00
|
|
|
</targetsetinfo>
|
|
|
|
|
|
|
|
<document targetdoc="manual">&manualtargets;</document>
|
|
|
|
</targetset>
|
|
|
|
EOF
|
|
|
|
'';
|
|
|
|
|
2010-08-11 14:28:53 +02:00
|
|
|
in rec {
|
|
|
|
|
2014-11-17 13:41:18 +01:00
|
|
|
# The NixOS options in JSON format.
|
2016-09-27 15:26:37 +02:00
|
|
|
optionsJSON = runCommand "options-json"
|
|
|
|
{ meta.description = "List of NixOS options in JSON format";
|
|
|
|
}
|
|
|
|
''
|
2014-11-17 13:41:18 +01:00
|
|
|
# Export list of options in different format.
|
|
|
|
dst=$out/share/doc/nixos
|
|
|
|
mkdir -p $dst
|
|
|
|
|
2014-11-17 13:44:52 +01:00
|
|
|
cp ${builtins.toFile "options.json" (builtins.unsafeDiscardStringContext (builtins.toJSON
|
2016-07-28 04:27:39 +02:00
|
|
|
(builtins.listToAttrs (map (o: { name = o.name; value = removeAttrs o ["name" "visible" "internal"]; }) optionsList'))))
|
2014-11-17 13:44:52 +01:00
|
|
|
} $dst/options.json
|
2014-11-17 13:41:18 +01:00
|
|
|
|
|
|
|
mkdir -p $out/nix-support
|
|
|
|
echo "file json $dst/options.json" >> $out/nix-support/hydra-build-products
|
|
|
|
''; # */
|
|
|
|
|
2010-08-11 14:28:53 +02:00
|
|
|
# Generate the NixOS manual.
|
2016-09-27 15:26:37 +02:00
|
|
|
manual = runCommand "nixos-manual"
|
|
|
|
{ inherit sources;
|
|
|
|
buildInputs = [ libxml2 libxslt ];
|
|
|
|
meta.description = "The NixOS manual in HTML format";
|
|
|
|
allowedReferences = ["out"];
|
|
|
|
}
|
|
|
|
''
|
2009-10-05 15:17:45 +02:00
|
|
|
# Generate the HTML manual.
|
2009-07-14 17:47:03 +02:00
|
|
|
dst=$out/share/doc/nixos
|
2014-06-30 14:56:10 +02:00
|
|
|
mkdir -p $dst
|
2014-08-25 19:08:12 +02:00
|
|
|
xsltproc \
|
nixos/doc: Allow refs from options to the manual
My first attempt to do this was to just use a conditional <refsection/>
in order to not create exact references in the manpage but create the
reference in the HTML manual, as suggested by @edolstra on IRC.
Later I went on to use <olink/> to reference sections of the manual, but
in order to do that, we need to overhaul how we generate the manual and
manpages.
So, that's where we are now:
There is a new derivation called "manual-olinkdb", which is the olinkdb
for the HTML manual, which in turn creates the olinkdb.xml file and the
manual.db. The former contains the targetdoc references and the latter
the specific targetptr elements.
The reason why I included the olinkdb.xml verbatim is that first of all
the DTD is dependent on the Docbook XSL sources and the references
within the olinkdb.xml entities are relative to the current directory.
So using a store path for that would end up searching for the manual.db
directly in /nix/store/manual.db.
Unfortunately, the <olinks/> that end up in the output file are
relative, so for example if you're clicking on one of these within the
PDF, the URL is searched in the current directory.
However, the sections from the olink's text are still valid, so we could
use an alternative URL for that in the future.
The manual doesn't contain any links, so even referencing the relative
URL shouldn't do any harm.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Cc: @edolstra
2016-04-11 18:29:00 +02:00
|
|
|
${manualXsltprocOptions} \
|
|
|
|
--stringparam target.database.document "${olinkDB}/olinkdb.xml" \
|
2017-06-28 19:02:33 +02:00
|
|
|
--nonet --output $dst/ \
|
|
|
|
${docbook5_xsl}/xml/xsl/docbook/xhtml/chunktoc.xsl \
|
|
|
|
${manual-combined}/manual-combined.xml
|
2009-09-18 17:10:37 +02:00
|
|
|
|
2012-07-25 17:54:24 +02:00
|
|
|
mkdir -p $dst/images/callouts
|
2014-08-09 16:30:44 +02:00
|
|
|
cp ${docbook5_xsl}/xml/xsl/docbook/images/callouts/*.gif $dst/images/callouts/
|
2013-01-09 13:43:57 +01:00
|
|
|
|
2009-07-14 17:47:03 +02:00
|
|
|
cp ${./style.css} $dst/style.css
|
2011-09-14 20:20:50 +02:00
|
|
|
|
2013-10-24 20:06:02 +02:00
|
|
|
mkdir -p $out/nix-support
|
|
|
|
echo "nix-build out $out" >> $out/nix-support/hydra-build-products
|
2014-09-10 15:03:49 +02:00
|
|
|
echo "doc manual $dst" >> $out/nix-support/hydra-build-products
|
2012-07-25 17:54:24 +02:00
|
|
|
''; # */
|
2013-10-24 20:06:02 +02:00
|
|
|
|
2010-08-11 14:28:53 +02:00
|
|
|
|
2016-09-27 15:26:37 +02:00
|
|
|
manualEpub = runCommand "nixos-manual-epub"
|
|
|
|
{ inherit sources;
|
|
|
|
buildInputs = [ libxml2 libxslt zip ];
|
|
|
|
}
|
|
|
|
''
|
2016-07-28 04:27:39 +02:00
|
|
|
# Generate the epub manual.
|
|
|
|
dst=$out/share/doc/nixos
|
|
|
|
|
|
|
|
xsltproc \
|
|
|
|
${manualXsltprocOptions} \
|
|
|
|
--stringparam target.database.document "${olinkDB}/olinkdb.xml" \
|
|
|
|
--nonet --xinclude --output $dst/epub/ \
|
2017-06-28 19:02:33 +02:00
|
|
|
${docbook5_xsl}/xml/xsl/docbook/epub/docbook.xsl \
|
|
|
|
${manual-combined}/manual-combined.xml
|
2016-07-28 04:27:39 +02:00
|
|
|
|
|
|
|
mkdir -p $dst/epub/OEBPS/images/callouts
|
2017-06-28 19:02:33 +02:00
|
|
|
cp -r ${docbook5_xsl}/xml/xsl/docbook/images/callouts/*.gif $dst/epub/OEBPS/images/callouts # */
|
2016-07-28 04:27:39 +02:00
|
|
|
echo "application/epub+zip" > mimetype
|
2016-08-01 11:02:41 +02:00
|
|
|
manual="$dst/nixos-manual.epub"
|
|
|
|
zip -0Xq "$manual" mimetype
|
|
|
|
cd $dst/epub && zip -Xr9D "$manual" *
|
|
|
|
|
|
|
|
rm -rf $dst/epub
|
2016-07-28 04:27:39 +02:00
|
|
|
|
|
|
|
mkdir -p $out/nix-support
|
2016-08-01 11:02:41 +02:00
|
|
|
echo "doc-epub manual $manual" >> $out/nix-support/hydra-build-products
|
2016-07-28 04:27:39 +02:00
|
|
|
'';
|
|
|
|
|
2010-08-11 14:28:53 +02:00
|
|
|
|
2016-09-27 15:26:37 +02:00
|
|
|
# Generate the NixOS manpages.
|
|
|
|
manpages = runCommand "nixos-manpages"
|
|
|
|
{ inherit sources;
|
|
|
|
buildInputs = [ libxml2 libxslt ];
|
|
|
|
allowedReferences = ["out"];
|
|
|
|
}
|
|
|
|
''
|
2009-10-05 15:17:45 +02:00
|
|
|
# Generate manpages.
|
2013-10-24 20:06:02 +02:00
|
|
|
mkdir -p $out/share/man
|
2017-06-28 19:02:33 +02:00
|
|
|
xsltproc --nonet \
|
2009-07-14 17:47:03 +02:00
|
|
|
--param man.output.in.separate.dir 1 \
|
|
|
|
--param man.output.base.dir "'$out/share/man/'" \
|
2009-10-06 01:15:06 +02:00
|
|
|
--param man.endnotes.are.numbered 0 \
|
2016-03-19 17:16:59 +01:00
|
|
|
--param man.break.after.slash 1 \
|
nixos/doc: Allow refs from options to the manual
My first attempt to do this was to just use a conditional <refsection/>
in order to not create exact references in the manpage but create the
reference in the HTML manual, as suggested by @edolstra on IRC.
Later I went on to use <olink/> to reference sections of the manual, but
in order to do that, we need to overhaul how we generate the manual and
manpages.
So, that's where we are now:
There is a new derivation called "manual-olinkdb", which is the olinkdb
for the HTML manual, which in turn creates the olinkdb.xml file and the
manual.db. The former contains the targetdoc references and the latter
the specific targetptr elements.
The reason why I included the olinkdb.xml verbatim is that first of all
the DTD is dependent on the Docbook XSL sources and the references
within the olinkdb.xml entities are relative to the current directory.
So using a store path for that would end up searching for the manual.db
directly in /nix/store/manual.db.
Unfortunately, the <olinks/> that end up in the output file are
relative, so for example if you're clicking on one of these within the
PDF, the URL is searched in the current directory.
However, the sections from the olink's text are still valid, so we could
use an alternative URL for that in the future.
The manual doesn't contain any links, so even referencing the relative
URL shouldn't do any harm.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Cc: @edolstra
2016-04-11 18:29:00 +02:00
|
|
|
--stringparam target.database.document "${olinkDB}/olinkdb.xml" \
|
2014-08-09 16:30:44 +02:00
|
|
|
${docbook5_xsl}/xml/xsl/docbook/manpages/docbook.xsl \
|
2017-06-28 19:02:33 +02:00
|
|
|
${manual-combined}/man-pages-combined.xml
|
2008-01-04 15:24:42 +01:00
|
|
|
'';
|
2015-09-24 11:47:00 +02:00
|
|
|
|
2011-09-14 20:20:50 +02:00
|
|
|
}
|