all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Raghav Gururajan <rvgn@disroot.org>
Cc: help-guix@gnu.org
Subject: Re: Updating Packages
Date: Wed, 17 Apr 2019 03:52:24 +0200	[thread overview]
Message-ID: <8736mh9z53.fsf@nckx> (raw)
In-Reply-To: <1502c5dbf040de32c954bb83875ab869@disroot.org>

[-- Attachment #1: Type: text/plain, Size: 810 bytes --]

Raghav Gururajan wrote:
> I had an idea/suggestion. How about adding "guix system -u" 
> feature to guix? So the difference between "guix system 
> reconfigure" and "guix system -u" would be; the former does the 
> reconfiguration cum upgrade process whereas the latter does just 
> the upgrade process to system packages in the existing 
> configuration.

But this arbitrary distinction doesn't make sense.

The system configuration file is a configuration file.  Like any 
other configuration file on your system, if you edit it and then 
invoke a new ’guix system’, Guix will use the current version of 
that configuration, not silently fall back to an out-of-date copy. 
That's how config files work.

Unless you're sendmail, and nobody wants to be sendmail.

Kind regards,

T G-R

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

  parent reply	other threads:[~2019-04-17  1:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-15 16:46 Updating Packages Raghav Gururajan
2019-04-15 18:48 ` Tobias Geerinckx-Rice
2019-04-15 18:50 ` Pierre Neidhardt
2019-04-16  4:36 ` Raghav Gururajan
2019-05-05 19:12   ` Chris Marusich
2019-04-16  4:43 ` Raghav Gururajan
2019-04-16 21:36   ` Joshua Branson
2019-04-17  1:52   ` Tobias Geerinckx-Rice [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-07-12 18:38 allan
2022-07-14 10:28 ` Munyoki Kilyungi
2022-07-14 13:42   ` Josselin Poiret

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=8736mh9z53.fsf@nckx \
    --to=me@tobias.gr \
    --cc=help-guix@gnu.org \
    --cc=rvgn@disroot.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.