From: Oleg Pykhalov <go.wigust@gmail.com>
To: Attic Hermit <fjdksl@cock.li>
Cc: help-guix@gnu.org
Subject: Re: Should I upgrade root user's guix too?
Date: Sat, 30 Sep 2017 03:38:47 +0300 [thread overview]
Message-ID: <87k20hnhpk.fsf@gmail.com> (raw)
In-Reply-To: <87poacuaa2.fsf@gmail.com> (Attic Hermit's message of "Wed, 27 Sep 2017 11:48:21 +0900")
Hello Attic,
Attic Hermit <fjdksl@cock.li> writes:
> Attic Hermit <fjdksl@cock.li> writes:
>
>>> #!/bin/sh
>>> GUIX_LATEST=/root/.config/guix/latest
>>> unlink $GUIX_LATEST && ln -s $(readlink $HOME/.config/guix/latest) $GUIX_LATEST
>
> To be sure your tip, I read the part of source code of guix pull and try
> to understand what it really do:
> http://git.savannah.gnu.org/cgit/guix.git/tree/guix/scripts/pull.scm
>
> and it seems that it only builds latest guix and make a symlink to
> ~/.config/guix/latest. Is that all? I'm little nervous that if I've
> missed something. If it is correct, then I can use your tip without
> doubt.
I got this idea after reading ‘(guix) Invoking guix pull’.
(1) Under the hood, ‘guix pull’ updates the ‘~/.config/guix/latest’
symbolic link to point to the latest Guix, and the ‘guix’ command
loads code from there. Currently, the only way to roll back an
invocation of ‘guix pull’ is to manually update this symlink to
point to the previous Guix.
Some folks just do ‘/root/.config/guix/latest -> ~/.config/guix/latest’
symlink. But I like to have a script which I could run manually as
needed.
next prev parent reply other threads:[~2017-09-30 0:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-22 11:08 Should I upgrade root user's guix too? Attic Hermit
2017-09-23 7:47 ` Chris Marusich
2017-09-23 8:17 ` Attic Hermit
2017-09-23 9:18 ` Chris Marusich
2017-09-23 13:05 ` Attic Hermit
2017-09-23 13:22 ` Adonay Felipe Nogueira
2017-09-24 18:01 ` Quiliro Ordonez Baca
2017-09-25 21:12 ` Chris Marusich
2017-09-26 18:10 ` Oleg Pykhalov
2017-09-27 2:04 ` Attic Hermit
2017-09-27 2:48 ` Attic Hermit
2017-09-30 0:38 ` Oleg Pykhalov [this message]
2017-09-30 3:47 ` Attic Hermit
2017-10-05 14:47 ` Hartmut Goebel
2017-10-06 5:36 ` Oleg Pykhalov
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=87k20hnhpk.fsf@gmail.com \
--to=go.wigust@gmail.com \
--cc=fjdksl@cock.li \
--cc=help-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 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.