all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: iyzsong@member.fsf.org (宋文武)
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>, bug-guix@gnu.org
Subject: New ‘guix pull’ dosen’t update the guix manual in GuixSD
Date: Sat, 09 Jun 2018 22:25:21 +0800	[thread overview]
Message-ID: <87fu1wyr3i.fsf@member.fsf.org> (raw)
In-Reply-To: <87y3fogt8e.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Sat, 09 Jun 2018 12:16:33 +0200")

ludo@gnu.org (Ludovic Courtès) writes:

> Hello Guix!
>
> For those who haven’t been following along on
> <https://debbugs.gnu.org/cgi/bugreport.cgi?bug=22629#35>, I have just
> pushed a new ‘guix pull’.
>
> To summarize, ~/.config/guix/latest no longer exists.  Instead
> ~/.config/guix/current is populated with a complete Guix (without
> ‘guix-daemon’ though), including an up-to-date manual and so on.
> ~/.config/guix/current is a regular profile, meaning that you can
> roll-back to a previously-pulled Guix and so on.

Great!


After run ‘guix pull’ twice, I have got ‘~/.config/guix/current’, then
use it to do a system reconfigure for ‘/etc/profile’.

But the guix manual doesn’t got updated, my ‘INFOPATH’ contains:

- /home/iyzsong/.guix-profile/share/info
- /run/current-system/profile/share/info
- /home/iyzsong/.config/guix/current/share/info
- /home/iyzsong/.guix-profile/share/info
- /run/current-system/profile/share/info

The last there are from the ‘export’ statement of ‘/etc/profile’, the
first two are added by ‘source’ the profiles.  Since there is a guix in
the system profile contains the old info manual, the current one won’t
be picked.

I think we should make ‘INFOPATH’ a search path of the ‘current’ guix
profile, so that it overrides previous ones.

  reply	other threads:[~2018-06-09 14:25 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-09 10:16 New ‘guix pull’ Ludovic Courtès
2018-06-09 14:25 ` 宋文武 [this message]
2018-06-10 19:33   ` New ‘guix pull’ dosen’t update the guix manual in GuixSD Ludovic Courtès
2018-06-11 11:27     ` 宋文武
2018-06-12 13:54       ` bug#31770: " Ludovic Courtès
2018-06-12 13:54       ` Ludovic Courtès
2018-06-11 11:27     ` bug#31770: " 宋文武
2018-06-10 19:33   ` Ludovic Courtès
2018-07-08 17:31 ` New ‘guix pull’ Pjotr Prins
2018-07-12  9:35 ` Chris Marusich
2018-07-12 11:04   ` Pjotr Prins
2018-07-12 11:12     ` Pjotr Prins
2018-07-12 12:35       ` New ‘guix pull’ - guile-sqlite3 problem Pjotr Prins
2018-07-12 12:43         ` Pjotr Prins
2018-07-18  5:32         ` Chris Marusich
2018-07-19  7:22           ` Pjotr Prins
2018-07-19  8:12             ` Chris Marusich
2018-07-12 14:17     ` New ‘guix pull’ Ricardo Wurmus
2018-07-12 14:20       ` Pjotr Prins
2018-07-12 14:29         ` Ricardo Wurmus
2018-07-12 16:44           ` Pjotr Prins
2018-07-13  8:39             ` New ‘guix pull’ /root/.config/current/bin/guix: Permission denied Pjotr Prins
2018-07-13  9:08               ` Pjotr Prins
2018-07-13  9:48                 ` Pjotr Prins
2018-07-13  9:54                   ` Pjotr Prins
2018-07-13 12:04               ` Ludovic Courtès
2018-07-13 15:24                 ` Pjotr Prins
2018-07-13  8:41             ` New ‘guix pull’ Pjotr Prins
2018-10-14 18:17           ` Pjotr Prins
2018-10-15 10:14             ` Ludovic Courtès
2018-07-12 16:01   ` Ludovic Courtès
2018-07-12 20:52     ` Brett Gilio

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

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

  git send-email \
    --in-reply-to=87fu1wyr3i.fsf@member.fsf.org \
    --to=iyzsong@member.fsf.org \
    --cc=bug-guix@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.