all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: James Smith <jsmith8365@protonmail.com>
Cc: help-guix@gnu.org
Subject: Re: readline problem
Date: Fri, 28 Jan 2022 12:22:51 +0100	[thread overview]
Message-ID: <87k0ekgkx4.fsf@elephly.net> (raw)
In-Reply-To: <ehyzL6MAB_tlOHUW8LG5zD7Y2XboF2PJqNi71Z7X7y7S97SMyNA9w6pSz9fv7H9wDppRMhNYTpY-LxjrTWzP8pNcNRpRbK_dKmTEshRjwug=@protonmail.com>


James Smith <jsmith8365@protonmail.com> writes:

> So it seems that guix pull should always be followed by guix package -u ?

No, I don’t think it’s correct to say that.  You can use your updated
Guix to do a lot of things that are completely unrelated to the state of
your default profile.

- install things to a different profile
- use “guix shell” for an ad-hoc environment
- use “guix pack” to build a portable archive
- reconfigure your system with your new Guix
…

There are also good reasons why you wouldn’t want to upgrade your
default profile every time you upgrade Guix.  Software in your default
profile may not actually build with the current version of Guix, or you
are perfectly happy with the version you have installed, or for
reproducibility reason you really want to stay with the current
well-known versions and only add a new independent tool…

There are problems with gradually building up state in a Guix profile by
consecutively adding packages installed with a different version of
Guix, but this is not a good reason to couple “guix pull” with upgrades
of your profile(s).

-- 
Ricardo


  reply	other threads:[~2022-01-28 11:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-15  8:13 readline problem jsmith via
2022-01-17 11:57 ` Ricardo Wurmus
2022-01-18 11:20   ` Wiktor Żelazny
2022-01-18 14:51     ` Ricardo Wurmus
2022-01-19 18:21       ` Wiktor Żelazny
2022-01-19 19:45         ` Ricardo Wurmus
2022-01-28 11:13           ` James Smith
2022-01-28 11:22             ` Ricardo Wurmus [this message]
2022-01-30  8:33               ` No upgrade after pull, and Guix philosophy (was: readline problem) Wiktor Żelazny
2022-01-30  8:53                 ` Ricardo Wurmus
2022-01-31 19:16                   ` Wiktor Żelazny
2022-01-31 19:26                     ` Ricardo Wurmus
2022-01-28 12:54             ` readline problem Dr. Arne Babenhauserheide

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=87k0ekgkx4.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=help-guix@gnu.org \
    --cc=jsmith8365@protonmail.com \
    /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.