nixos/manual: inline the single footnote

this is a lot easier than adding footnote support for just the one
instance. if a use case for footnotes appears in the future (e.g. if we
wanted to render the nixpkgs manual with nixos-render-docs as well) this
decision should be reevaluated.

pennae 65d749c8 2ad93ab1

Changed files
+17 -18
nixos
doc
manual
configuration
from_md
configuration
+7 -7
nixos/doc/manual/configuration/modularity.section.md
···
defined in other modules. This is what the `config` function argument is
for: it contains the complete, merged system configuration. That is,
`config` is the result of combining the configurations returned by every
-
module [^1] . For example, here is a module that adds some packages to
+
module. (If you're wondering how it's possible that the (indirect) *result*
+
of a function is passed as an *input* to that same function: that's
+
because Nix is a "lazy" language --- it only computes values when
+
they are needed. This works as long as no individual configuration
+
value depends on itself.)
+
+
For example, here is a module that adds some packages to
[](#opt-environment.systemPackages) only if
[](#opt-services.xserver.enable) is set to `true` somewhere else:
···
{ imports = [ (netConfig "nixos.localdomain") ]; }
```
-
-
[^1]: If you're wondering how it's possible that the (indirect) *result*
-
of a function is passed as an *input* to that same function: that's
-
because Nix is a "lazy" language --- it only computes values when
-
they are needed. This works as long as no individual configuration
-
value depends on itself.
+10 -11
nixos/doc/manual/from_md/configuration/modularity.section.xml
···
<literal>config</literal> function argument is for: it contains the
complete, merged system configuration. That is,
<literal>config</literal> is the result of combining the
-
configurations returned by every module <footnote>
-
<para>
-
If you’re wondering how it’s possible that the (indirect)
-
<emphasis>result</emphasis> of a function is passed as an
-
<emphasis>input</emphasis> to that same function: that’s because
-
Nix is a <quote>lazy</quote> language — it only computes values
-
when they are needed. This works as long as no individual
-
configuration value depends on itself.
-
</para>
-
</footnote> . For example, here is a module that adds some packages
-
to <xref linkend="opt-environment.systemPackages" /> only if
+
configurations returned by every module. (If you’re wondering how
+
it’s possible that the (indirect) <emphasis>result</emphasis> of a
+
function is passed as an <emphasis>input</emphasis> to that same
+
function: that’s because Nix is a <quote>lazy</quote> language — it
+
only computes values when they are needed. This works as long as no
+
individual configuration value depends on itself.)
+
</para>
+
<para>
+
For example, here is a module that adds some packages to
+
<xref linkend="opt-environment.systemPackages" /> only if
<xref linkend="opt-services.xserver.enable" /> is set to
<literal>true</literal> somewhere else:
</para>