maurice/snix
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

* Translate Unicode quote characters to ASCII equivalents when

Browse source 
generating NEWS.txt.
This commit is contained in:
Eelco Dolstra 2006-10-06 09:03:39 +00:00
parent 3815d2d463
commit b3fc016061
2 changed files with 16 additions and 12 deletions
Download patch file Download diff file Expand all files Collapse all files

4
doc/manual/quote-literals.xsl
View file

@ -37,4 +37,8 @@
</xsl:element> </xsl:element>
</xsl:template> </xsl:template>
<xsl:template match="text()">
<xsl:value-of select="translate(., '‘’“”—', concat(&quot;`'&quot;, '&quot;&quot;-'))" />
</xsl:template>
</xsl:stylesheet> </xsl:stylesheet>

24
doc/manual/release-notes.xml
View file

@ -533,8 +533,8 @@ xlink:href='http://catamaran.labs.cs.uu.nl/dist/nix/channels-v3/nixpkgs-unstable
hash.)</para></listitem> hash.)</para></listitem>
<listitem><para>Big cleanups and simplifications of the basic store <listitem><para>Big cleanups and simplifications of the basic store
semantics. The notion of "closure store expressions" is gone (and semantics. The notion of “closure store expressions” is gone (and
so is the notion of "successors"); the file system references of a so is the notion of “successors”); the file system references of a
store path are now just stored in the database.</para> store path are now just stored in the database.</para>
<para>For instance, given any store path, you can query its closure: <para>For instance, given any store path, you can query its closure:
@ -544,7 +544,7 @@ $ nix-store -qR $(which firefox)
... lots of paths ...</screen> ... lots of paths ...</screen>
Also, Nix now remembers for each store path the derivation that Also, Nix now remembers for each store path the derivation that
built it (the "deriver"): built it (the “deriver”):
<screen> <screen>
$ nix-store -qR $(which firefox) $ nix-store -qR $(which firefox)
@ -588,7 +588,7 @@ $ nix-store -q --referrers-closure \
<listitem><para>One-click installation :-) It is now possible to <listitem><para>One-click installation :-) It is now possible to
install any top-level component in Nixpkgs directly, through the web install any top-level component in Nixpkgs directly, through the web
- see, e.g., <link — see, e.g., <link
xlink:href='http://catamaran.labs.cs.uu.nl/dist/nixpkgs-0.8/' />. xlink:href='http://catamaran.labs.cs.uu.nl/dist/nixpkgs-0.8/' />.
All you have to do is associate All you have to do is associate
<filename>/nix/bin/nix-install-package</filename> with the MIME type <filename>/nix/bin/nix-install-package</filename> with the MIME type
@ -670,10 +670,10 @@ $ nix-env -f .../i686-linux.nix -i -E 'x: x.firefoxWrapper'</screen>
</listitem> </listitem>
<listitem><para>The garbage collector now finally deletes paths in <listitem><para>The garbage collector now finally deletes paths in
the right order (i.e., topologically sorted under the the right order (i.e., topologically sorted under the “references”
<quote>references</quote> relation), thus making it safe to relation), thus making it safe to interrupt the collector without
interrupt the collector without risking a store that violates the risking a store that violates the closure
closure invariant.</para></listitem> invariant.</para></listitem>
<listitem><para>Likewise, the substitute mechanism now downloads <listitem><para>Likewise, the substitute mechanism now downloads
files in the right order, thus preserving the closure invariant at files in the right order, thus preserving the closure invariant at
@ -737,10 +737,10 @@ $ nix-env -f .../i686-linux.nix -i -E 'x: x.firefoxWrapper'</screen>
<listitem><para>Binary patching. When upgrading components using <listitem><para>Binary patching. When upgrading components using
pre-built binaries (through nix-pull / nix-channel), Nix can pre-built binaries (through nix-pull / nix-channel), Nix can
automatically download and apply binary patches to already installed automatically download and apply binary patches to already installed
components instead of full downloads. Patching is "smart": if there components instead of full downloads. Patching is “smart”: if there
is a *sequence* of patches to an installed component, Nix will use is a <emphasis>sequence</emphasis> of patches to an installed
it. Patches are currently generated automatically between Nixpkgs component, Nix will use it. Patches are currently generated
(pre-)releases.</para></listitem> automatically between Nixpkgs (pre-)releases.</para></listitem>
<listitem><para>Simplifications to the substitute <listitem><para>Simplifications to the substitute
mechanism.</para></listitem> mechanism.</para></listitem>