From: "Wiktor Żelazny" <wz@freeshell.de>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: James Smith <jsmith8365@protonmail.com>, help-guix@gnu.org
Subject: No upgrade after pull, and Guix philosophy (was: readline problem)
Date: Sun, 30 Jan 2022 09:33:32 +0100 [thread overview]
Message-ID: <20220130083332.2uxx2pv2tqis7ldy@wzguix> (raw)
In-Reply-To: <87k0ekgkx4.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 1075 bytes --]
On Fri, Jan 28, 2022 at 12:22:51PM +0100, Ricardo Wurmus wrote:
> 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…
This sounds rather brittle: you need to keep things in your head. It’s
like being a liar: you need to remember what lie you told to what
person. And then you make an error and your byzantine construction (of
software versions or lies) falls down.
Is this in the spirit of Guix at all? I mean, is this functional package
management? Wouldn’t it be nicer to have manifests support an additional
(optional) field, viz. guix commit corresponding to given package, and
manage your profile using that explicit manifest file? Or aren’t
inferiors suitable for such purpose?
WŻ
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 963 bytes --]
next prev parent reply other threads:[~2022-01-30 8:35 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
2022-01-30 8:33 ` Wiktor Żelazny [this message]
2022-01-30 8:53 ` No upgrade after pull, and Guix philosophy (was: readline problem) 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=20220130083332.2uxx2pv2tqis7ldy@wzguix \
--to=wz@freeshell.de \
--cc=help-guix@gnu.org \
--cc=jsmith8365@protonmail.com \
--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 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.