max/nix-super
1
0
Fork 0
mirror of https://github.com/privatevoid-net/nix-super.git synced 2024-11-25 23:36:16 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions

allowedRequisites: Drop stdenv mention

Browse source 
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:
Eelco Dolstra 2014-08-28 18:26:01 +02:00
parent b5da80e627
commit 9eddf6f0b6
2 changed files with 3 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
doc/manual/release-notes.xml
View file

@ -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>

5
doc/manual/writing-nix-expressions.xml
View file

@ -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>