unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Alex Sassmannshausen <alex.sassmannshausen@gmail.com>
To: bug-guix <bug-guix@gnu.org>
Subject: Re: First time guix build
Date: Tue, 22 Jan 2013 23:49:32 +0000	[thread overview]
Message-ID: <87sj5s7p83.fsf@gmail.com> (raw)
In-Reply-To: <87d2ww5110.fsf@gnu.org>

That seems to have worked a treat — thanks for your help.

Whilst reading the published manual on the GNU Guix website I came across the following three sentences that could maybe be improved (their all in section 3.1):
'Instead of referring to these directories, users have their own profile, which points to the packages that they actually want to use. That profile is normally stored in $HOME/.guix-profile, and each user has its own profile. '
Would probably sound better and read easier if it were:
'Instead of referring to these directories, users each have their own profile, which points to the packages that they actually want to use. These profiles are stored within each user's own home directory, at $HOME/.guix-profile.'

The nextparagraph could be rewritten as (though maybe just unnecessary rewording):
For example, alice installs GCC 4.7.2. As a result, gcc in her profile, /home/alice/.guix-profile/bin/gcc would point to /nix/store/xxx-gcc-4.7.2/bin/gcc. Now, on the same machine, bob had already installed GCC 4.8.0. Bob's profile simply continues to point to /nix/store/xxx-gcc-4.8.0/bin/gcc; i.e. both versions of GCC coexist on the same system without any interference.

Finally, what I think is a typ-o:
…if the guix-package processed is terminated… 
should be
…if the guix-package process is terminated…

I also just now, when re-configuring with a different store directory, noticed that there might be a typ-o in the localstatedir param example. It currently says:
The default values are --with-store-dir=/nix/store and --localstatedir=/nix/var.
But I think it should read
[…] and --localstatedir=/var/nix.

Hope this helps, let me know if it's better to provide this kind of thing in a different fashion.

Best,

Alex

Ludovic Courtès <ludo@gnu.org> writes:

> Hello,
>
> Alex Sassmannshausen <alex.sassmannshausen@gmail.com> skribis:
>
>> I'm trying my hand at building guix and have run into some
>> problems. I've cloned the git repository à la:
>> $ git clone git://git.savannah.gnu.org/guix.git
>> followed by 
>> $ cd guile; autoreconf -vif
>> $ ./configure && make
>
> You actually need to run the ./bootstrap script instead of ‘autoreconf’.
>
> It does a couple more things: it initializes a Git sub-module that
> points to the Nix repo, and copies the subset of Nix source code that we
> need in the nix/ directory.
>
> Let us know how it works!
>
> Ludo’.

  reply	other threads:[~2013-01-22 23:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-22 21:55 First time guix build Alex Sassmannshausen
2013-01-22 22:02 ` Ludovic Courtès
2013-01-22 23:49   ` Alex Sassmannshausen [this message]
2013-01-23 14:44     ` Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87sj5s7p83.fsf@gmail.com \
    --to=alex.sassmannshausen@gmail.com \
    --cc=bug-guix@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).