From: Brian Cully via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Jelle Licht <jlicht@fsfe.org>
Cc: "Ludovic Courtès" <ludo@gnu.org>,
63921@debbugs.gnu.org,
"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Subject: bug#63921: Activation snippets in reverse order, prevent boot
Date: Wed, 07 Jun 2023 18:02:39 -0400 [thread overview]
Message-ID: <87zg5b7wqj.fsf@psyduck.jhoto.kublai.com> (raw)
In-Reply-To: <87r0qni2vo.fsf@fsfe.org>
Jelle Licht <jlicht@fsfe.org> writes:
> Thanks for the workaround! Is this "thou shall delete N times,
> and
> _exactly_ N times" effect of the recently pushed change
> functioning as
> intended? It imho seems pretty brittle and verbose compared to
> how
> things were before.
We could add a ‘delete-all’ in addition to the existing ‘delete’
behavior. Alternately, we could change ‘delete’ back to deleting
everything and adding ‘delete-one’. Or have both ‘delete-all’ and
‘delete-one’ where ‘delete’ is a deprecated alias for ‘delete-all’
to add a path forward for older configs.
Of the three I'm most partial to the last, though I love none of
them. I keep thinking the right solution is to have a delete that
can match with a predicate, but then why not just use ‘filter’ or
‘remove’?
-bjc
next prev parent reply other threads:[~2023-06-07 22:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 8:15 bug#63921: Activation snippets in reverse order, prevent boot Ludovic Courtès
2023-06-06 9:58 ` Ludovic Courtès
2023-06-07 8:57 ` pelzflorian (Florian Pelz)
2023-06-07 9:19 ` pelzflorian (Florian Pelz)
2023-06-07 9:30 ` pelzflorian (Florian Pelz)
2023-06-07 17:44 ` Jelle Licht
2023-06-07 22:02 ` Brian Cully via Bug reports for GNU Guix [this message]
2023-06-07 23:07 ` pelzflorian (Florian Pelz)
2023-06-17 13:59 ` pelzflorian (Florian Pelz)
2023-06-26 19:26 ` bug#63921: Patch proposed Felix Lechner via Bug reports for GNU Guix
2023-09-01 11:43 ` bug#63921: Activation snippets in reverse order, prevent boot Maxim Cournoyer
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=87zg5b7wqj.fsf@psyduck.jhoto.kublai.com \
--to=bug-guix@gnu.org \
--cc=63921@debbugs.gnu.org \
--cc=bjc@spork.org \
--cc=jlicht@fsfe.org \
--cc=ludo@gnu.org \
--cc=pelzflorian@pelzflorian.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.
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).