allowedRequisites: Drop stdenv mention
I don't think it's a good idea to use allowedRequisites for stdenv, so don't mention it here.
This commit is contained in:
parent
b5da80e627
commit
9eddf6f0b6
2 changed files with 3 additions and 8 deletions
|
@ -18,10 +18,8 @@
|
|||
<varname>allowedReferences</varname>. But instead of only enforcing
|
||||
to explicitly specify the immediate references, it requires the
|
||||
derivation to specify all the dependencies recursively (hence the
|
||||
name, requisites) that are used by the resulting output. This is
|
||||
used in NixOS when rebuilding the stdenv on Linux to ensure that the
|
||||
resulting stdenv doesn't have any surprising dependency, e.g. on
|
||||
bootstrapTools.</para></listitem>
|
||||
name, requisites) that are used by the resulting
|
||||
output.</para></listitem>
|
||||
|
||||
</itemizedlist>
|
||||
|
||||
|
|
|
@ -1583,10 +1583,7 @@ allowedReferences = [ foobar ];
|
|||
enforces that the output of a derivation cannot have any other
|
||||
runtime dependency than <varname>foobar</varname>, and in addition
|
||||
it enforces that <varname>foobar</varname> itself doesn't
|
||||
introduce any other dependency itself. This is used in NixOS when
|
||||
rebuilding the stdenv on Linux to ensure that the resulting stdenv
|
||||
doesn't have any surprising dependency, e.g. on
|
||||
bootstrapTools.</para></listitem>
|
||||
introduce any other dependency itself.</para></listitem>
|
||||
|
||||
</varlistentry>
|
||||
|
||||
|
|
Loading…
Reference in a new issue