unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: "Wiktor Żelazny" <wz@freeshell.de>
Cc: James Smith <jsmith8365@protonmail.com>, help-guix@gnu.org
Subject: Re: No upgrade after pull, and Guix philosophy (was: readline problem)
Date: Mon, 31 Jan 2022 20:26:57 +0100	[thread overview]
Message-ID: <8735l3aeni.fsf@elephly.net> (raw)
In-Reply-To: <20220131191634.cc3g6asd5mv7t4ml@wzguix>


Wiktor Żelazny <wz@freeshell.de> writes:

> [[PGP Signed Part:Undecided]]
> On Sun, Jan 30, 2022 at 09:53:14AM +0100, Ricardo Wurmus wrote:
>>
>> Wiktor Żelazny <wz@freeshell.de> writes:
>>
>> > This sounds rather brittle: you need to keep things in your head.
>>
>> I don’t follow.  I don’t see what you’re referring to as “brittle” and
>> what you need to keep in your head.
>
> When upgrading your packages you need to remember every time which ones
> you want to keep at their current versions (in the broad sense) and, to
> my understanding, juggle with regexpes, so that they’re excluded from an
> upgrade. What if you upgrade them by accident? How do you roll-back and
> how do you know to which corresponding Guix commit you should roll-back
> to?
>
> A manifest would let you be more organized. You can put comments there,
> you can manage it with version control.

Sure, that’s why they exist.  But it’s fine to offer both interfaces.

The imperative interface exists because it is common and does not
require much learning at all.  When the convenience it provides is
outmatched by the downsides of imperative package management users can
migrate to manifests.

-- 
Ricardo


  reply	other threads:[~2022-01-31 20:06 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               ` 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 [this message]
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

  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=8735l3aeni.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=help-guix@gnu.org \
    --cc=jsmith8365@protonmail.com \
    --cc=wz@freeshell.de \
    /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.
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).