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

svn path=/nixpkgs/trunk/; revision=9308

This commit is contained in:
Eelco Dolstra 2007-09-11 21:42:42 +00:00
parent bd0e895bad
commit 04ca4bb7ea
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/release-notes.xml
View File

@ -15,7 +15,7 @@
<listitem><para>The standard build environment <listitem><para>The standard build environment
(<literal>stdenv</literal>) is now pure on the (<literal>stdenv</literal>) is now pure on the
<literal>x86_64-linux</literal> and <literal>powerpc-linux</literal> <literal>x86_64-linux</literal> and <literal>powerpc-linux</literal>
platforms, just like <literal>i686-linux</literal>. (Purity means platforms, just as on <literal>i686-linux</literal>. (Purity means
that building and using the standard environment has no dependencies that building and using the standard environment has no dependencies
outside of the Nix store. For instance, it doesn’t require an outside of the Nix store. For instance, it doesn’t require an
external C compiler such as <filename>/usr/bin/gcc</filename>.) external C compiler such as <filename>/usr/bin/gcc</filename>.)
@ -29,7 +29,7 @@
<listitem><para>Hook variables in the generic builder are now <listitem><para>Hook variables in the generic builder are now
executed using the <function>eval</function> shell command. This executed using the <function>eval</function> shell command. This
has a major advantage: you can write hooks directly in Nix has a major advantage: you can write hooks directly in Nix
expressions. For instance, rather than write a builder like this: expressions. For instance, rather than writing a builder like this:
<programlisting> <programlisting>
source $stdenv/setup source $stdenv/setup