From: "Ludovic Courtès" <ludo@gnu.org>
To: Raghav Gururajan <rvgn@disroot.org>
Cc: guix-devel@gnu.org
Subject: Re: "guix system -u" and "guix system --list-packages"
Date: Tue, 16 Apr 2019 22:35:14 +0200 [thread overview]
Message-ID: <875zrdd6yl.fsf@gnu.org> (raw)
In-Reply-To: <d2f9aaf311017e305c753aac4de2a19a@disroot.org> (Raghav Gururajan's message of "Tue, 16 Apr 2019 10:41:59 +0000")
Hello!
"Raghav Gururajan" <rvgn@disroot.org> skribis:
> Idea of adding following features to Guix.
>
> 1) Dedicated "guix system -u" separated from "guix system reconfigure". So the difference between "guix system reconfigure" and "guix system -u" would be; the former does changes to system configuration (including adding/upgrading system packages) whereas the latter just upgrades system packages without making changes to system configuration.
This command:
guix package -p /run/current-system/profile -u
almost does that, but eventually fails because /run/current-system is
read-only. Hmm…
Now, in principle, upgrading the system profile without upgrading system
services is not a good idea, because it could lead to inconsistencies.
For instance, the GNOME service consists of a set of Shepherd services
and D-Bus services, but it also populates the system profile. All these
things need to be in sync.
> 2) "guix system --list-packages" lists all system packages in current system generation. Could also add additional parameter (like "guix system --list-packages #sys-gen") to list system packages in a different available system generation.
What about:
guix package -p /run/current-system/profile -I
?
Thanks,
Ludo’.
prev parent reply other threads:[~2019-04-16 20:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 10:41 "guix system -u" and "guix system --list-packages" Raghav Gururajan
2019-04-16 15:34 ` znavko
2019-04-16 20:35 ` Ludovic Courtès [this message]
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=875zrdd6yl.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@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 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).