From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: "Tobias Geerinckx-Rice" <me@tobias.gr>, "Ludovic Courtès" <ludo@gnu.org>
Cc: 54691@debbugs.gnu.org, Maxime Devos <maximedevos@telenet.be>,
56599@debbugs.gnu.org
Subject: bug#54691: fortune-mod propagates various non-nice things
Date: Thu, 04 Aug 2022 19:12:05 +0200 [thread overview]
Message-ID: <8ddb8ad9db66e89534184df1a2b20bd3124672fc.camel@gmail.com> (raw)
In-Reply-To: <E61C2DFA-D252-43C8-B946-5805C1C24847@tobias.gr>
Am Donnerstag, dem 04.08.2022 um 15:37 +0000 schrieb Tobias Geerinckx-
Rice:
> > To me use of ‘deprecated-package’ in this case is just to ensure
> > that users who run ‘guix upgrade’ will transparently get
> > ‘fortune-jkirchartz’. I don’t have a strong opinion though.
>
> I believe what Liliana meant is that it's worse to 'transparently'
> upgrade to a data package that doesn't provide the 'fortune' command
> at all (or conversely, an implementation of the command that doesn't
> propagate the actual fortune data), than it is to signal to users
> through an error message that something's up and they need to stop
> and think.
>
> (Er, that's a lot more words to put in someone's mouth than I
> intended to, sorry :-)
I'm not saying either option is worse than the other, just that we
can't pick both in a manner that provides a functioning package, and
that transparently upgrading to a package that does nothing is a pretty
bad option. We could transparently upgrade to daikichi, but that'd
just say "no fortunes found" because FORTUNE_PATH will be empty. Other
options would include a metapackage (also rejected by Maxime) or
providing a dummy fortune-mod package that fails at build with a
helpful message and is disabled in CI (came up as a shower thought).
Cheers
next prev parent reply other threads:[~2022-08-04 17:17 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-03 13:09 bug#54691: fortune-mod propagates various non-nice things Maxime Devos
2022-04-03 17:26 ` Liliana Marie Prikler
2022-04-03 18:12 ` Maxime Devos
2022-04-03 18:41 ` Maxime Devos
2022-04-04 10:41 ` Maxime Devos
2022-07-19 19:20 ` Maxime Devos
2022-07-20 4:31 ` Liliana Marie Prikler
2022-07-20 8:45 ` Maxime Devos
2022-07-20 16:57 ` Liliana Marie Prikler
2022-07-20 18:50 ` Maxime Devos
2022-04-03 18:20 ` Maxime Devos
2022-07-14 1:30 ` Maxim Cournoyer
2022-07-14 13:00 ` Csepp
2022-07-14 14:55 ` Maxim Cournoyer
2022-07-19 18:54 ` Maxime Devos
2022-07-19 19:45 ` Maxime Devos
2022-07-23 15:06 ` bug#54691: [PATCH v3 2/6] gnu: Add daikichi Liliana Marie Prikler
2022-07-23 15:06 ` bug#54691: [PATCH 1/5] " Liliana Marie Prikler
2022-07-23 15:06 ` bug#54691: [PATCH v2 " Liliana Marie Prikler
2022-07-23 15:11 ` bug#54691: [PATCH v2 2/5] gnu: Add fortunes-jkirchartz Liliana Marie Prikler
2022-07-23 15:11 ` bug#54691: [PATCH v3 3/6] " Liliana Marie Prikler
2022-07-23 15:11 ` bug#54691: [PATCH 2/5] " Liliana Marie Prikler
2022-07-23 19:54 ` Maxime Devos
2022-07-23 20:43 ` Liliana Marie Prikler
2022-07-23 21:41 ` Maxime Devos
2022-07-23 21:52 ` Liliana Marie Prikler
2022-07-23 22:13 ` Maxime Devos
2022-07-23 19:56 ` Maxime Devos
2022-07-23 20:53 ` Liliana Marie Prikler
2022-07-23 22:01 ` Maxime Devos
2022-07-24 1:09 ` bokr
2022-07-23 15:13 ` bug#54691: [PATCH v2 3/5] gnu: Remove fortune-mod Liliana Marie Prikler
2022-08-03 13:43 ` [bug#56599] bug#54691: fortune-mod propagates various non-nice things Ludovic Courtès
2022-08-03 17:09 ` Liliana Marie Prikler
2022-08-04 12:23 ` Ludovic Courtès
2022-08-04 15:37 ` [bug#56599] " Tobias Geerinckx-Rice via Guix-patches via
2022-08-04 17:12 ` Liliana Marie Prikler [this message]
2022-08-04 19:58 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2022-08-06 23:01 ` [bug#56599] " bokr
2022-08-06 23:05 ` Maxime Devos
2022-08-30 10:22 ` bug#56599: " Liliana Marie Prikler
2022-07-23 15:13 ` bug#54691: [PATCH v3 4/6] gnu: Remove fortune-mod Liliana Marie Prikler
2022-07-23 15:13 ` bug#54691: [PATCH 3/5] " Liliana Marie Prikler
2022-07-23 19:58 ` Maxime Devos
2022-07-23 20:54 ` Liliana Marie Prikler
2022-07-23 15:16 ` bug#54691: [PATCH v3 5/6] gnu: Remove rinutils Liliana Marie Prikler
2022-07-23 15:16 ` bug#54691: [PATCH 4/5] " Liliana Marie Prikler
2022-07-23 15:16 ` bug#54691: [PATCH v2 " Liliana Marie Prikler
2022-07-24 10:33 ` paren--- via Bug reports for GNU Guix
2022-07-24 11:27 ` Liliana Marie Prikler
2022-07-23 15:17 ` bug#54691: [PATCH v3 6/6] gnu: Remove shlomif-cmake-modules Liliana Marie Prikler
2022-07-23 15:17 ` bug#54691: [PATCH v2 5/5] " Liliana Marie Prikler
2022-07-23 15:17 ` bug#54691: [PATCH " Liliana Marie Prikler
2022-08-13 9:26 ` bug#54691: [PATCH v3 1/6] build-system: copy: Support #:tests? Liliana Marie Prikler
2022-08-28 22:16 ` Liliana Marie Prikler
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=8ddb8ad9db66e89534184df1a2b20bd3124672fc.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=54691@debbugs.gnu.org \
--cc=56599@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=maximedevos@telenet.be \
--cc=me@tobias.gr \
/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.