From: Pjotr Prins <pjotr.public12@thebird.nl>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: New ‘guix pull’
Date: Thu, 12 Jul 2018 18:44:56 +0200 [thread overview]
Message-ID: <20180712164456.o3nhmhqobo5idilg@thebird.nl> (raw)
In-Reply-To: <87muuwr0i9.fsf@elephly.net>
On Thu, Jul 12, 2018 at 04:29:02PM +0200, Ricardo Wurmus wrote:
>
> Pjotr Prins <pjotr.public12@thebird.nl> writes:
>
> > On Thu, Jul 12, 2018 at 04:17:32PM +0200, Ricardo Wurmus wrote:
> >> “guix pull” updates its own profile only. It updates
> >> ~/.config/guix/current, so you need to use Guix from
> >> ~/.config/guix/current/bin.
> >
> > And it says so after guix pull. It is easy to forget however.
> >
> > Why don't we (also) add it to the default guix profile? To most users
> > this would make sense. No point in running guix pull if you don't want
> > to update guix itself - right?
>
> It does update Guix itself. The “guix” package, however, should
> generally not be installed into a user profile, because it is always
> necessarily *older* than the version of Guix that you are using to
> install it (unless you’re using “--with-source” to use a more recent
> tarball).
Hmmm. I don't understand. I would think it the other way round: the
guix package you install is newer than the running daemon. But, no
matter. Maybe we should just accentuate that guix gets its own independent
profile. That I can understand ;). So it should *never* be in the user
profile. Not even by accident.
Pj.
next prev parent reply other threads:[~2018-07-12 16:45 UTC|newest]
Thread overview: 29+ 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 ` New ‘guix pull’ dosen’t update the guix manual in GuixSD 宋文武
2018-06-10 19:33 ` Ludovic Courtès
2018-06-11 11:27 ` 宋文武
2018-06-12 13:54 ` 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 [this message]
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
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=20180712164456.o3nhmhqobo5idilg@thebird.nl \
--to=pjotr.public12@thebird.nl \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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).