diff options
| author | Eelco Dolstra <e.dolstra@tudelft.nl> | 2005-01-12T10·27+0000 |
|---|---|---|
| committer | Eelco Dolstra <e.dolstra@tudelft.nl> | 2005-01-12T10·27+0000 |
| commit | 7d75616f2ca4e72db7088767e052b66de5718a80 (patch) | |
| tree | bfacb5788ded60f654efedfbf4a175eb5f400bfe /doc/manual/introduction.xml | |
| parent | 6af4a5a71ffee704c4760be4259d69bb7e21b870 (diff) | |
* NEWS and manual update for release 0.7.
Diffstat (limited to 'doc/manual/introduction.xml')
| -rw-r--r-- | doc/manual/introduction.xml | 9 |
1 files changed, 8 insertions, 1 deletions
diff --git a/doc/manual/introduction.xml b/doc/manual/introduction.xml index 35f18dee2c..5eb43f3d77 100644 --- a/doc/manual/introduction.xml +++ b/doc/manual/introduction.xml @@ -75,7 +75,7 @@ be adapted easily to achieve similar policies.</para></listitem> <listitem><para>Nix component builds aim to be <quote>pure</quote>; that is, unaffected by anything other than the declared dependencies. -This means that if a component was built succesfully once, it can be +This means that if a component was built successfully once, it can be rebuilt again on another machine and the result will be the same. We cannot <emphasis>guarantee</emphasis> this (e.g., if the build depends on the time-of-day), but Nix (and the tools in the Nix Packages @@ -113,6 +113,13 @@ software deployment also apply here: for instance, the ability trivially to have multiple configurations at the same time, or the ability to do rollbacks.</para></listitem> +<listitem><para>Nix can efficiently upgrade between different versions +of a component through <emphasis>binary patching</emphasis>. If +patches are available on a server, and you try to install a new +version of some component, Nix will automatically apply a patch (or +sequence of patches), if available, to transform the installed +component into the new version.</para></listitem> + </itemizedlist> </para> |