From: "Raghav Gururajan" <raghavgururajan@disroot.org>
To: guix-devel@gnu.org
Subject: Thoughts on making Guix even better
Date: Sun, 23 Feb 2020 02:49:12 +0000 [thread overview]
Message-ID: <e3bb8df9372b1992d1e669db08e4e0b5@disroot.org> (raw)
Hello Guix!
I have been thinking about this for a long time and would like to share it now.
The transactional upgrades and roll-backs are available to both Guix Package and Guix System. But I see a important difference which might be crucial to guix's development and use.
GUIX PACKAGE:
The guix package transactions are MODULAR. That is, you can upgrade packages selectively. For example, you can upgrade all packages except one/few (or) only upgrade one/few.
GUIX SYSTEM:
The guix system transactions are NON-MODULAR. That is, you cannot selectively reconfigure certain parts of the system. For example, you either reconfigure the system as a whole (or) you do not reconfigure the system at all.
IMPLICATIONS:
Lets assume we have 5 packages in profile. Package 1, 3 and 5 has non-critical updates. Package 4 has non-critical update but it breaks. Package 2 has critical update (CVE). We can either upgrade all packages except package 4 (or) we can upgrade only package 2.
Lets assume we have 5 services/packages in system. Package/Service 1, 3 and 5 has non-critical updates. Package/Service 4 has non-critical update but it breaks. Package/Service 2 has critical update (CVE). Now, when we reconfigure the system, all packages/services will upgrade, package/service 4 will break the system. We can of course do '--roll-back' and take the system to previous working state. But that will leave the system with critical vulnerability. Therefore, we cannot reconfigure package/service 2 or any other parts of the system, until the package/service 4 is fixed. This window/gap puts guix system at great risk and instability.
SUGGESTION:
We can brain-storm and implement a way to make guix system transactions modular. Any ideas?
Thank you!
Regards,
Raghav "RG" Gururajan.
next reply other threads:[~2020-02-23 2:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-23 2:49 Raghav Gururajan [this message]
2020-02-23 20:28 ` Thoughts on making Guix even better Jonathan Frederickson
2020-03-08 20:54 ` Ludovic Courtès
2020-03-09 6:18 ` Gábor Boskovits
2020-03-09 7:28 ` Konrad Hinsen
[not found] <24c65c56c37b309c108f75fb9e3e4681866e7fac.camel@student.tugraz.at>
2020-02-23 17:14 ` Leo Prikler
2020-03-01 10:26 ` Raghav Gururajan
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=e3bb8df9372b1992d1e669db08e4e0b5@disroot.org \
--to=raghavgururajan@disroot.org \
--cc=guix-devel@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.