diff --git a/doc/manual/build-farm.xml b/doc/manual/build-farm.xml index 9a6345896..3b973188d 100644 --- a/doc/manual/build-farm.xml +++ b/doc/manual/build-farm.xml @@ -56,7 +56,7 @@ build farm, since: TODO The sources of the Nix build farm are at . +xlink:href='https://svn.nixos.org/repos/nix/release/trunk'/>. @@ -85,7 +85,7 @@ nix@scratchy.labs.cs.uu.nl i686-linux /home/nix/.ssh/id_scratchy_auto An example build hook can be found in the Nix build farm sources: . It should be suitable for most purposes, with maybe some minor adjustments. It uses ssh and rsync to copy the build inputs and outputs and diff --git a/doc/manual/installation.xml b/doc/manual/installation.xml index d61c0c230..bf4331d75 100644 --- a/doc/manual/installation.xml +++ b/doc/manual/installation.xml @@ -42,25 +42,22 @@ platforms as well.
Obtaining Nix The easiest way to obtain Nix is to download a source distribution. RPMs +xlink:href="http://nixos.org/">source distribution. RPMs for Red Hat, SuSE, and Fedora Core are also available. Alternatively, the most recent sources of Nix can be obtained from its Subversion +xlink:href="https://svn.nixos.org/repos/nix/nix/trunk">Subversion repository. For example, the following command will check out the latest revision into a directory called nix: -$ svn checkout https://svn.cs.uu.nl:12443/repos/trace/nix/trunk nix +$ svn checkout https://svn.nixos.org/repos/nix/nix/trunk nix Likewise, specific releases can be obtained from the tags -directory of the repository. If you don't have Subversion, you -can also download an automatically generated compressed -tar-file of the head revision of the trunk. +xlink:href="https://svn.nixos.org/repos/nix/nix/tags">tags +directory of the repository.
@@ -161,7 +158,7 @@ options.
Installing from RPMs RPM packages of Nix can be downloaded from . These RPMs should work for most +xlink:href="http://nixos.org/" />. These RPMs should work for most fairly recent releases of SuSE and Red Hat Linux. They have been known to work work on SuSE Linux 8.1 and 9.0, and Red Hat 9.0. In fact, it should work on any RPM-based Linux distribution based on @@ -193,12 +190,12 @@ $ rm -rf /nix/var You can install the latest stable version of Nix through Nix itself by subscribing to the channel , +xlink:href="http://nixos.org/releases/nix/channels/nix-stable" />, or the latest unstable version by subscribing to the channel . +xlink:href="http://nixos.org/releases/nix/channels/nix-unstable" />. You can also do a one-click installation by clicking on the package links at . +xlink:href="http://nixos.org/releases/full-index-nix.html" />.
diff --git a/doc/manual/package-management.xml b/doc/manual/package-management.xml index 9ab181692..be0d5f21b 100644 --- a/doc/manual/package-management.xml +++ b/doc/manual/package-management.xml @@ -38,7 +38,7 @@ to end-user applications like Mozilla Firefox. (Nix is however not tied to the Nix Package collection; you could write your own Nix expressions based on it, or completely new ones.) You can download the latest version from . +xlink:href='http://nixos.org/releases/full-index-nixpkgs.html' />. Assuming that you have downloaded and unpacked a release of Nix Packages, you can view the set of available packages in the release: @@ -118,15 +118,15 @@ available somewhere. This is done using the containing a manifest describing what binaries are available. This URL should correspond to the Nix Packages release that you’re using. For instance, if you obtained a release from , then -you should do: +xlink:href='http://nixos.org/releases/nixpkgs/nixpkgs-0.12pre11712-4lrp7j8x' +/>, then you should do: -$ nix-pull http://nix.cs.uu.nl/dist/nix/nixpkgs-0.6pre1554/MANIFEST +$ nix-pull http://nixos.org/releases/nixpkgs/nixpkgs-0.12pre11712-4lrp7j8x/MANIFEST If you then issue the installation command, it should start downloading binaries from nix.cs.uu.nl, instead of building +class='fqdomainname'>nixos.org, instead of building them from source. This might still take a while since all dependencies must be downloaded, but on a reasonably fast connection such as an DSL line it’s on the order of a few minutes. @@ -458,7 +458,7 @@ URL. nix-channel --add, e.g., -$ nix-channel --add http://nix.cs.uu.nl/dist/nix/channels-v3/nixpkgs-unstable +$ nix-channel --add http://nixos.org/releases/nixpkgs/channels/nixpkgs-unstable subscribes you to a channel that always contains that latest version of the Nix Packages collection. (Instead of @@ -496,20 +496,19 @@ available in the subscribed channels. Often, when you want to install a specific package (e.g., from the Nix -Packages collection or from our release server), -subscribing to a channel is a bit cumbersome. And channels don’t help -you at all if you want to install an older version of a package than -the one provided by the current contents of the channel, or a package -that has been removed from the channel. That’s when -one-click installs come in handy: you can just go -to the web page that contains the package, click on it, and it will be -installed with all the necessary dependencies. +xlink:href="http://nixos.org/releases/nixpkgs/nixpkgs-unstable/">Nix +Packages collection), subscribing to a channel is a bit +cumbersome. And channels don’t help you at all if you want to install +an older version of a package than the one provided by the current +contents of the channel, or a package that has been removed from the +channel. That’s when one-click installs come in +handy: you can just go to the web page that contains the package, +click on it, and it will be installed with all the necessary +dependencies. For instance, you can go to -— or to any older release of Nix Packages — and click on any link for +xlink:href="http://nixos.org/releases/nixpkgs/nixpkgs-unstable/" /> — +or to any older release of Nix Packages — and click on any link for the individual packages for your platform (say, subversion-1.4.0 for i686-linux). The first time you do diff --git a/doc/manual/writing-nix-expressions.xml b/doc/manual/writing-nix-expressions.xml index 840eb120d..60e8a2f34 100644 --- a/doc/manual/writing-nix-expressions.xml +++ b/doc/manual/writing-nix-expressions.xml @@ -731,9 +731,9 @@ stdenv.mkDerivation { xlink:href='http://www.ietf.org/rfc/rfc2396.txt'>RFC 2396 can be written as is, without quotes. For instance, the string - "https://svn.cs.uu.nl:12443/dist/trace/trace-nix-trunk.tar.bz2" + "http://example.org/foo.tar.bz2" can also be written as - https://svn.cs.uu.nl:12443/dist/trace/trace-nix-trunk.tar.bz2. + http://example.org/foo.tar.bz2.