unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: Mathieu Othacehe <othacehe@gnu.org>, 52805@debbugs.gnu.org
Subject: [bug#52805] [PATCH] substitute: Add a ‘--clear-cache’ option.
Date: Wed, 05 Jan 2022 21:59:44 +0100	[thread overview]
Message-ID: <87czl5kif3.fsf_-_@gnu.org> (raw)
In-Reply-To: <87pmphhg8q.fsf@nckx> (Tobias Geerinckx-Rice's message of "Mon, 27 Dec 2021 22:20:16 +0100")

Hello,

Tobias Geerinckx-Rice <me@tobias.gr> skribis:

> Mathieu Othacehe 写道:

[...]

>> Moreover this script is an internal undocumented tool,
>> so I'm not in favor of adding user commands to it.

+1

> The point was to have a little command I could ask other users to run,
> that's guaranteed to clear the correct directory, and doesn't involve
> a spooky rm (which saves some back-and-forth :-).

In which case do users have to ‘rm -rf ~/.cache/guix/substitute’?

That directory is only used by ‘guix weather’.  In that case,
‘--clear-cache’ could be added to ‘guix weather’ maybe?

Now, ideally there would not be any cache-related option because the
cache would always be valid.  If it’s not, it would be nice to see how
that can be improved or mitigated.

Thoughts?

Ludo’.




  parent reply	other threads:[~2022-01-05 21:00 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 [this message]
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
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=87czl5kif3.fsf_-_@gnu.org \
    --to=ludo@gnu.org \
    --cc=52805@debbugs.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).