NixOS/nix-pills
NixOS/nix-pills
1
0
Fork 0
mirror of https://github.com/NixOS/nix-pills synced 2024-09-19 04:00:13 -04:00
Code Activity

fix import issues in pill 20

Browse source
This commit is contained in:
Nicolas Dudebout 2018-04-08 21:35:48 -04:00 committed by John Ericson
parent a3c3d6d889
commit 4bdce7aa10
2 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
pills/20-basic-dependencies-and-hooks.xml
View file

@ -36,7 +36,7 @@
For the simplest dependencies where the current package directly needs another, we use the <varname>buildInputs</varname> attribute.
This is exactly the pattern in taught with our builder in <link linkend="generic-builders">Pill 8</link>.
To demo this, lets build GNU Hello, and then another package which provides a shell script that <command>exec</command>s it.
<screen><xi:include href="./20/two-hellos.txt" parse="text" /></screen>
<screen><xi:include href="./20/two-hellos.nix" parse="text" /></screen>
</para>
<para>
@ -63,7 +63,7 @@
Nix itself handles this just fine, understanding various dependency <firstterm>closures</firstterm> as covered in previous builds.
But what about the conveniences that <varname>buildInputs</varname> provides, namely accumulating in <envar>pkgs</envar> environment variable and inclusion of <filename><replaceable>pkg</replaceable>/bin</filename> directories on the <envar>PATH</envar>?
For this, Stdenv provides the <varname>propagatedBuildInputs</varname>:
<screen><xi:include href="./20/two-hellos.txt" parse="text" /></screen>
<screen><xi:include href="./20/two-hellos.nix" parse="text" /></screen>
See how the intermediate package has a <varname>propagatedBuildInputs</varname> dependency, but the wrapper only needs a <varname>buildInputs</varname> dependency on the intermediary.
</para>

0
pills/20/propagated-build-inputs-3.bash → pills/20/propagated-build-inputs-2.bash
View file