From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nikita Karetnikov Subject: Re: [PATCH] doc: Improve wording and fix typos in "Introduction" and "Requirements". Date: Sat, 25 May 2013 04:30:27 +0400 Message-ID: <87k3mnnboc.fsf@karetnikov.org> References: <87r4gwh8jm.fsf@karetnikov.org> <87ip28wfj1.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([208.118.235.92]:60177) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ug2KX-0000nh-5U for bug-guix@gnu.org; Fri, 24 May 2013 20:27:36 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Ug2KO-0007Ki-SO for bug-guix@gnu.org; Fri, 24 May 2013 20:27:29 -0400 In-Reply-To: <87ip28wfj1.fsf@gnu.org> ("Ludovic =?utf-8?Q?Court=C3=A8s=22'?= =?utf-8?Q?s?= message of "Fri, 24 May 2013 17:42:26 +0200") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org To: Ludovic =?utf-8?Q?Court=C3=A8s?= Cc: bug-guix@gnu.org --==-=-= Content-Type: multipart/mixed; boundary="=-=-=" --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable > But anyway, the normal way to use Texinfo is like TeX: you use ASCII > quotes, and it does the right thing (see the PDF output, and the Info > output if you=E2=80=99re using makeinfo 5.x.) I know, I was talking about the output of 'makeinfo --html'. I'm using 4.13. > There seems to be some paragraph filling at least here. Yes, I did that to keep the length under 79 characters and to avoid the lines which consist of a couple of words. > Could you rearrange the patch to avoid paragraph filling, so that only > the parts that were really changed show up? Is it OK? --=-=-= Content-Type: text/x-diff; charset=utf-8 Content-Disposition: attachment; filename=0001-doc-Improve-wording-and-fix-typos-in-Introduction-an.patch Content-Transfer-Encoding: quoted-printable From=2091df1e8c54d824807a1681b381e76cf25d40538a Mon Sep 17 00:00:00 2001 From: Nikita Karetnikov Date: Sat, 25 May 2013 00:04:00 +0000 Subject: [PATCH] doc: Improve wording and fix typos in "Introduction" and "Requirements". * doc/guix.texi (Introduction, Requirements): Rephrase and fix typos. =2D-- doc/guix.texi | 50 +++++++++++++++++++++++++------------------------- 1 files changed, 25 insertions(+), 25 deletions(-) diff --git a/doc/guix.texi b/doc/guix.texi index cf54fe4..28b8d84 100644 =2D-- a/doc/guix.texi +++ b/doc/guix.texi @@ -96,42 +96,41 @@ Documentation License.'' GNU Guix@footnote{``Guix'' is pronounced like ``geeks'', or ``=C9=A1i=CB= =90ks'' using the international phonetic alphabet (IPA).} is a functional package management tool for the GNU system. Package management consists =2Din all the activities that relate to building packages from source, =2Dhonoring the build-time and run-time dependencies on packages, +of all activities that relate to building packages from sources, +preserving their build-time and run-time dependencies, installing packages in user environments, upgrading installed packages to new versions or rolling back to a previous set, removing unused software packages, etc. =20 @cindex functional package management =2DThe term @dfn{functional} refers to a specific package management =2Ddiscipline. In Guix, the package build and installation process is seen =2Das a function, in the mathematical sense: that function takes inputs, =2Dsuch as build scripts, a compiler, and libraries depended on, and =2Dreturns the installed package. As a pure function, its result depends +The term @dfn{functional} refers to a specific set of package management +features. In Guix, the package build and installation process is seen +as a function, in the mathematical sense. That function takes inputs, +such as build scripts, a compiler, and libraries, and +returns an installed package. As a pure function, its result depends solely on its inputs---for instance, it cannot refer to software or scripts that were not explicitly passed as inputs. A build function =2Dalways produces the same result when passed a given set of inputs. Last =2Dbut not least, a build function cannot alter the system's environment in +always produces the same result when passed the same set of inputs. It +cannot alter the system's environment in any way; for instance, it cannot create, modify, or delete files outside of its build and installation directories. This is achieved by running =2Dbuild processes in dedicated ``chroots'', where only their explicit =2Dinputs are visible. +build processes in isolated environments (or @dfn{chroots}), where only th= eir +explicit inputs are visible. =20 @cindex store =2DThe result of package build functions is @dfn{cached} in the file +The result of package's build functions is @dfn{cached} in the file system, in a special directory called @dfn{the store} (@pxref{The =2DStore}). Each package is installed in a directory of its own, in the =2Dstore---by default under @file{/nix/store}. The directory name contains =2Da hash of all the inputs used to build that package; thus, changing an +Store}). Each installed package has its own directory there. +The directory name contains +a hash of all build inputs of that package; thus, changing an input yields a different directory name. =20 This approach is the foundation of Guix's salient features: support for =2Dtransactional package upgrades and rollback, per-user installation, and +transactional package upgrades and rollbacks, per-user installation, and garbage collection of packages (@pxref{Features}). =20 =2DGuix has a command-line interface allowing users to build, install, +Guix has a command-line interface which allows users to build, install, upgrade, and remove packages, as well as a Scheme programming interface. =2DThe remainder of this manual describes them. =20 Last but not least, Guix is used to build a distribution of the GNU system, with many GNU and non-GNU free software packages. @xref{GNU @@ -175,19 +174,20 @@ following packages are also needed: @item @url{http://gcc.gnu.org, GCC's g++} @end itemize =20 =2DWhen a working installation of the Nix package manager is available, you +When a working installation of @url{http://nixos.org/nix/, the Nix package +manager} is available, you can instead configure Guix with @code{--disable-daemon}. In that case, =2D@url{http://nixos.org/nix/, Nix} replaces the three dependencies above. +Nix replaces the three dependencies above. =20 Guix is compatible with Nix, so it is possible to share the same store between both. To do so, you must pass @command{configure} not only the same @code{--with-store-dir} value, but also the same =2D@code{--localstatedir} value (the latter is essential because it =2Dspecifies where the database that store meta-data about the store is =2Dlocated, among other things.) The default values are +@code{--localstatedir} value. The latter is essential because it +specifies where the database that stores metadata about the store is +located, among other things. The default values are @code{--with-store-dir=3D/nix/store} and @code{--localstatedir=3D/nix/var}. =2DNote that @code{--disable-daemon} is orthogonal and is not required if =2Dyour goal is to share the same store as Nix. +Note that @code{--disable-daemon} is not required if +your goal is to share the store with Nix. =20 @node Setting Up the Daemon @section Setting Up the Daemon =2D-=20 1.7.5.4 --=-=-=-- --==-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQIcBAEBAgAGBQJRoAYnAAoJEM+IQzI9IQ38WV8QAIVO1k8Igo3D+oqVR/Tlz6JQ ZPF7sEJpoocRzEILt7BOGey3lHOjrab90RsjXQNBmMgNBZWJnVh2gGsG8/8x14oQ lvXTN9JituWmYPC7JqM58oyweohSDKRrVyo0wwvXZ6jcW0nx1bwJa+ldizvDAy10 eoaVYyNyF7Wvlb8iB/z6JDr3OzC6VeNN8ydHtW1hdKqq4/zGZgJvhlzANFgWgCLV k4yoR87UjLEXMiEGrpIyjmkZZqx4XR00wkiReyT/tlU0h8MohJyRFyzIXL55Tqb2 tQKaZBGCON6lGzwhbGbYI/P6bDoOlZaztgtfZwfeNd9mBZ8D+x9tjo99yo4nZo1K D2BXzzscGmbc3NpbZIEWMtl8cGGBID5gyFU7kbHNrV4ub30qu1INRos4j2W72Sdo U3037AI9eIhEuDY/euK6o6p7EUrIDnCFh2p5q/979Ws65s6JzE/I+Xgph5lC3C3I 4hAAMie8ruShwuuY9z2LjaPPwx064o/ufDojX2R7jwJWCVOeiy+ZgAyEeIZrzHPF c+jO2vwhcwJdkdUg9Zuv8IV3gUOd+Zz7Ts5hyU0KfRYq9OfpBv3orqSN2WTAJLJv QNgIvZtWQmEDc2tgltWeuYvxv6+zuUtvwbEFbPVPsy7RuDFI1eNTgSSqNOM8wywT PA5djhs8A6PQDFM+lK7l =zpDj -----END PGP SIGNATURE----- --==-=-=--