JakeHillion/nixpkgs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

nixpkgs manual: advise against overriding whole phases

Browse Source 
I've seen that mistake at least a few times already, e.g.
https://github.com/NixOS/nixpkgs/pull/26209#issuecomment-305925562
It might perhaps seem counter-intuitive if one doesn't know nixpkgs well.
This commit is contained in:
Vladimír Čunát 2017-06-03 11:24:18 +02:00
parent b520c30d9e
commit 8c6fada372
No known key found for this signature in database
GPG Key ID: E747DF1F9575A3AA
1 changed files with 7 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/stdenv.xml
View File

@ -318,7 +318,13 @@ containing some shell commands to be executed, or by redefining the
shell function shell function
<varname><replaceable>name</replaceable>Phase</varname>. The former <varname><replaceable>name</replaceable>Phase</varname>. The former
is convenient to override a phase from the derivation, while the is convenient to override a phase from the derivation, while the
latter is convenient from a build script.</para> latter is convenient from a build script.
However, typically one only wants to <emphasis>add</emphasis> some
commands to a phase, e.g. by defining <literal>postInstall</literal>
or <literal>preFixup</literal>, as skipping some of the default actions
may have unexpected consequences.
</para>
<section xml:id="ssec-controlling-phases"><title>Controlling <section xml:id="ssec-controlling-phases"><title>Controlling