unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice <me@tobias.gr>
To: 35683@debbugs.gnu.org
Subject: bug#35683: wishlist: addessing statefulness of .cache(s)
Date: Sat, 11 May 2019 13:45:03 +0200	[thread overview]
Message-ID: <87zhntxlj4.fsf@nckx> (raw)
In-Reply-To: <878svdh2ec.fsf@roquette.mug.biscuolo.net>

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

ehlo Giovanni,

Giovanni Biscuolo wrote:
> AFAIU unfortunately we have application/library state all over 
> .cache(s)
> that sometimes crashes software *and* trying to fix this 
> upstream it's
> _not_ an option [1]

Oh.  That's… disappointing to say the least, since these are both 
upstream bugs that Guix can't fix :-(

What exactly did you ask?  What was their response?

> often users have to delete something in some .cache by guessing, 
> "just"
> to solve some strange software crash (this is common to all 
> distros)

I have never had to do this, ever.

> maybe an activation service extension proposed by Ricardo (see 
> above)
> is the right solution: I'll try to make a summary of prevoius
> discussions on this topic on guix-devel to help address this 
> (class of)
> issue(s)... sorry I cannot help coding it

We can randomly delete whole caches in the user's stead but it's 
never the ‘right’ solution.  Only the application can manage its 
caches properly.  I still hope this is possible in both cases 
here.

Kind regards,

T G-R

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

  parent reply	other threads:[~2019-05-11 11:46 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 [this message]
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

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=87zhntxlj4.fsf@nckx \
    --to=me@tobias.gr \
    --cc=35683@debbugs.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).