unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alex Kost <alezost@gmail.com>
To: Alex Vong <alexvong1995@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: 2 (possible) problems in documentation
Date: Sun, 01 Nov 2015 00:17:40 +0300	[thread overview]
Message-ID: <87wpu2kaa3.fsf@gmail.com> (raw)
In-Reply-To: <CADrxHD-+D1V0LZZUaFTKdz7yx-hqPxbSG=sLmpfSALWBeLDhgg@mail.gmail.com> (Alex Vong's message of "Sat, 31 Oct 2015 19:27:57 +0800")

Alex Vong (2015-10-31 14:27 +0300) wrote:

> Hi,
>
> I hit several problems when I followed the documentation. Please see
> if it is a real issue or just my misunderstandings.
>
> 1. In <https://www.gnu.org/software/guix/manual/guix.html#X11-Fonts>,
> it saids "Essential font packages include gs-fonts, font-dejavu, and
> font-gnu-freefont.". But I think "font-gnu-freefont" has been renamed
> to "font-gnu-freefont-ttf", so this has to be changed.

I think this on-line manual is for the current version (0.8.3).  The
typo you mention was fixed in the git repo:
<http://git.savannah.gnu.org/cgit/guix.git/commit/?id=8fe5b1d1d1d188cbc6eb1b644fdc0d9fff255d4e>

> 2. In
> <https://www.gnu.org/software/guix/manual/guix.html#Running-Guix-Before-It-Is-Installed>,
> it said "To that end, all the command-line tools can be used even if
> you have not run make install.". However, in the case of "guix pull",
> it is not true. Even if "guix pull" does run properly, it will not
> update the source tree you have downloaded, so you end up with running
> the original compiled version of Guix. Obviously, I was a victim :)

Sorry, I don't understand what you mean here.  "guix pull" can't update
the source tree you downloaded.  It fetches the latest guix source,
compiles it, put it to the store and link "~/.config/guix/latest" to it.
Then the Guix code from this directory when you run "guix ..." commands.

If you use the described "pre-inst-env" method, the code from the git
directory is used instead, and running "guix pull" doesn't effect
".../pre-inst-env guix" commands in any way.  Here instead of "guix
pull" you use "git pull" and "make".

-- 
Alex

  reply	other threads:[~2015-10-31 21:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-31 11:27 2 (possible) problems in documentation Alex Vong
2015-10-31 21:17 ` Alex Kost [this message]
2015-11-01  3:22   ` Alex Vong
2015-11-01 15:13     ` Alex Kost
2015-11-01 15:30     ` Mathieu Lirzin
2015-11-01 15:43       ` Mathieu Lirzin
2015-11-03  4:46         ` Alex Vong
2015-11-03  8:58           ` Ludovic Courtès
2015-11-03  9:01           ` JavaScript on web site Ludovic Courtès
2015-11-03 12:52             ` Mathieu Lirzin

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=87wpu2kaa3.fsf@gmail.com \
    --to=alezost@gmail.com \
    --cc=alexvong1995@gmail.com \
    --cc=guix-devel@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).