From: Danny Milosavljevic <dannym@scratchpost.org>
To: Giovanni Biscuolo <g@xelera.eu>
Cc: 35683@debbugs.gnu.org
Subject: bug#35683: wishlist: addessing statefulness of .cache(s)
Date: Sun, 12 May 2019 11:32:42 +0200 [thread overview]
Message-ID: <20190512113242.583f9229@scratchpost.org> (raw)
In-Reply-To: <878svdh2ec.fsf@roquette.mug.biscuolo.net>
[-- Attachment #1: Type: text/plain, Size: 956 bytes --]
> --8<---------------cut here---------------start------------->8---
> What should we do about this? For gdm I think it would make sense to
> add an activation service extension that clears the gdm user’s home
> directory. And more generally, maybe we should offer a generic cache
> cleaner service.
I don't like that workaround much. I mean for the time being I guess it's
OK, but let's file bug reports upstream so they are aware of the problem.
Better would be if the cache directory contained a "cache-protocol-version"
file or something and make the client program heed it and make it clear the
cache if it's the wrong version, without any Guix special case (the problem
is not not Guix-specific anyway).
It's not exactly difficult. Most of the time the bug reports just don't
get filed--and cache invalidation is always an afterthought when
implementing a cache (sadly).
If they say no we can still keep the workaround.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-05-12 9:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-11 7:32 bug#35683: wishlist: addessing statefulness of .cache(s) Giovanni Biscuolo
2019-05-11 7:43 ` Julien Lepiller
2019-05-11 11:51 ` Tobias Geerinckx-Rice
2019-05-11 7:50 ` Giovanni Biscuolo
2019-05-11 11:45 ` Tobias Geerinckx-Rice
2019-05-11 12:59 ` Giovanni Biscuolo
2019-05-12 21:29 ` swedebugia
2019-05-12 9:32 ` Danny Milosavljevic [this message]
2019-05-14 7:47 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190512113242.583f9229@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=35683@debbugs.gnu.org \
--cc=g@xelera.eu \
/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.