all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 35683@debbugs.gnu.org
Subject: bug#35683: wishlist: addessing statefulness of .cache(s)
Date: Tue, 14 May 2019 09:47:55 +0200	[thread overview]
Message-ID: <87tvdx32ac.fsf@gnu.org> (raw)
In-Reply-To: <20190512113242.583f9229@scratchpost.org> (Danny Milosavljevic's message of "Sun, 12 May 2019 11:32:42 +0200")

Hi Danny,

Danny Milosavljevic <dannym@scratchpost.org> skribis:

> 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).

I’d be surprised if applications and libraries using ~/.cache such as
Mesa didn’t have some versioning mechanism allowing them to detect stale
cache files.  Overall, Guix isn’t special in that respect.

The problem we experienced with Mesa shader caches are probably not
Guix-specific.  I think we should try to gather more info about the
stale .cache files that trigger a Mesa crash so that we can make a
useful bug report to the Mesa developers.

(I’m saying this as someone who did not experience the crash, heheh.  :-))

Thoughts?

Thanks,
Ludo’.

      reply	other threads:[~2019-05-14  7:49 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
2019-05-14  7:47   ` Ludovic Courtès [this message]

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=87tvdx32ac.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=35683@debbugs.gnu.org \
    --cc=dannym@scratchpost.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 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.