unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Mathieu Othacehe <othacehe@gnu.org>, 52805@debbugs.gnu.org
Subject: [bug#52805] [PATCH] substitute: Add a ‘--clear-cache’ option.
Date: Tue, 11 Jan 2022 19:00:19 +0100	[thread overview]
Message-ID: <87a6g2qgo0.fsf@nckx> (raw)
In-Reply-To: <87sftuv3q2.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 882 bytes --]

Hiya Ludo',

Ludovic Courtès 写道:
> For the same reason as ‘guix substitute’: caching allows it to 
> send only
> requests for which it doesn’t already know the answer.

Thanks!  The problem is this reason doesn't make sense.

N.B. I agree it's an acceptable trade-off for ‘guix substitute’, 
which has different operating parameters.

When I run ‘guix weather’ twice in a row, I am *never* interested 
in reviewing the stale numbers I got the first time (or worse: a 
mix of stale and new numbers).  I don't care if the data is very 
fresh: I am asking for fresher.

Caching is never to my advantage: it is ‘saving’ only the work I 
asked it to perform, against my wishes.  ‘Look how fast I fed you 
possibly bogus data against your will!’ is not an impressive 
boast.

Is my concern clear?  Reasonable?

Kind regards,

T G-R

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

  reply	other threads:[~2022-01-11 18:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-26 16:21 [bug#52805] [PATCH] substitute: Add a ‘--clear-cache’ option Tobias Geerinckx-Rice via Guix-patches via
2021-12-27 21:12 ` Mathieu Othacehe
2021-12-27 21:20   ` Tobias Geerinckx-Rice via Guix-patches via
2021-12-29 16:49     ` zimoun
2022-01-05 20:59     ` Ludovic Courtès
2022-01-05 22:41       ` Tobias Geerinckx-Rice via Guix-patches via
2022-01-11 12:47         ` Ludovic Courtès
2022-01-11 18:00           ` Tobias Geerinckx-Rice via Guix-patches via [this message]
2022-01-12 21:04             ` Ludovic Courtès

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=87a6g2qgo0.fsf@nckx \
    --to=guix-patches@gnu.org \
    --cc=52805@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    --cc=me@tobias.gr \
    --cc=othacehe@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 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).