multi-step installation

· Added pre- and post-installation hooks to the installation phase.
· No attempt to install staged files is made if the build doesn't stage any files.

1 files changed, 23 insertions, 0 deletions

diff --git a/manual.en.html b/manual.en.html
index 4d1c780..17f213a 100755
--- a/manual.en.html
+++ b/manual.en.html
@@ -594,6 +594,29 @@ be added as prerequisites.</p></dd>
 <dd><p>This preprocesses files that need to be preprocessed before projects are
 built.</p></dd>
 
+<dt><var>postinstall</var></dt>
+<dd><p>You may add a recipe to <var>postinstall</var> if there are commands
+that need to be run on the target system after the files have been installed.
+This will typically be commands that modify existing files on the target
+system. Normally “<samp>make install</samp>” runs <var>postinstall</var> after
+installing the files when <var>DESTDIR</var> is empty, but skips it when a
+directory is specified in <var>DESTDIR</var>, because such commands need to be
+run on the target system, not on a build server. Installing users can override
+this default behaviour by setting <var>do_postinstall</var> to
+“<samp>true</samp>” or “<samp>false</samp>”.</p></dd>
+
+<dt><var>preinstall</var></dt>
+<dd><p>This is like <var>postinstall</var> except that it's run before the
+files are installed, not after. Installing users can control it with
+<var>do_preinstall</var>.</p></dd>
+
+<dt><var>install_files</var></dt>
+<dd><p>You may add a recipe to <var>install_files</var> if any files have to be
+written, deleted or moved after the staged directory tree has been copied.
+Avoid using this if possible. It's better to stage all the files correctly
+under the staging directory in the build phase, but this hook exists if you
+really need it for some workaround.</p></dd>
+
 <dt><var>configure</var></dt>
 <dd><p>“<samp>make configure</samp>” is used to set values in the
 <a href="#configuration">persistent configuration</a> and to set up a