Skip to content

Commit

Permalink
doc/configuration: tidy up text around #23130 changes
Browse files Browse the repository at this point in the history
  • Loading branch information
vcunat committed Feb 26, 2017
1 parent 78d3a11 commit a50222b
Showing 1 changed file with 13 additions and 5 deletions.
18 changes: 13 additions & 5 deletions doc/configuration.xml
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ will prevent installation if any of the following criteria are
true:</para>

<itemizedlist>
<listitem><para>The packages is thought to be broken, and has had
<listitem><para>The package is thought to be broken, and has had
its <literal>meta.broken</literal> set to
<literal>true</literal>.</para></listitem>

Expand All @@ -23,7 +23,14 @@ true:</para>
<literal>meta.knownVulnerabilities</literal>.</para></listitem>
</itemizedlist>

<para>Each of these criteria can be altering the nixpkgs
<para>Note that all this is checked during evaluation already,
and the check includes any package that is evaluated.
In particular, all build-time dependencies are checked.
<literal>nix-env -qa</literal> will (attempt to) hide any packages
that would be refused.
</para>

<para>Each of these criteria can be altered in the nixpkgs
configuration.</para>

<para>The nixpkgs configuration for a NixOS system is set in the
Expand Down Expand Up @@ -68,10 +75,11 @@ configuration file located at
add <literal>allowBroken = true;</literal> to your user's
configuration file, like this:

<programlisting>
<programlisting>
{
allowBroken = true;
}</programlisting>
}
</programlisting>
</para></listitem>
</itemizedlist>
</section>
Expand Down Expand Up @@ -156,7 +164,7 @@ configuration file located at
</title>

<para>There are several ways to tweak how Nix handles a package
which has been marked as unfree.</para>
which has been marked as insecure.</para>

<itemizedlist>
<listitem><para>
Expand Down

0 comments on commit a50222b

Please sign in to comment.