unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: Leo Prikler <leo.prikler@student.tugraz.at>,
	"Jan \(janneke\) Nieuwenhuizen" <janneke@gnu.org>,
	43920-done@debbugs.gnu.org
Subject: bug#43920: [SHEPHERD PATCH] shepherd: Move log file to XDG_CACHE_DIR.
Date: Wed, 18 Nov 2020 22:35:43 +0100	[thread overview]
Message-ID: <87wnyijqkw.fsf@gnu.org> (raw)
In-Reply-To: <87pn55cmdy.fsf@gnu.org> ("Ludovic Courtès"'s message of "Mon, 26 Oct 2020 11:27:53 +0100")

Hi,

Ludovic Courtès <ludo@gnu.org> skribis:

> Efraim Flashner <efraim@flashner.co.il> skribis:
>
>> On October 24, 2020 4:15:33 PM UTC, "Ludovic Courtès" <ludo@gnu.org> wrote:
>
> [...]
>
>>>>> The previous location wasn’t perfect, but the proposed one isn’t
>>>>> great
>>>>> either: one can generally assume “rm -rf ~/.cache” won’t lose
>>>>> anything
>>>>> that cannot be reconstructed, and the log is something that cannot be
>>>>> reconstructed.
>
> [...]
>
>> I don't think it's really data, it's not like it belongs in something/share. As another data point keybase writes its (verbose) logs in .cache/keybase.
>
> To me the question whether it’s OK to lose the log.  In a way, storing
> the log in ~/.cache akin to storing it in /tmp.
>
> If we agree on that, then we have the choice between ~/.local/share
> aka. XDG_DATA_HOME (like Xorg does), or maybe using ~/.local/var/log or
> something similar that goes beyond XDG?

I pushed a variant of your patch that uses XDG_DATA_HOME instead:

  https://git.savannah.gnu.org/cgit/shepherd.git/commit/?id=c6382a6898f2851d78b675f209787c5ff9ad4320

There’s a now ‘%user-log-dir’ so it’ll be easier to adjust going
forward if we change our mind.

Thanks,
Ludo’.




  reply	other threads:[~2020-11-18 21:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-11  9:20 [bug#43920] [SHEPHERD PATCH] shepherd: Move log file to XDG_CACHE_DIR Efraim Flashner
2020-10-22 14:23 ` Ludovic Courtès
2020-10-23 22:17 ` Leo Prikler
2020-10-24 16:15   ` Ludovic Courtès
2020-10-24 16:51     ` Efraim Flashner
2020-10-26 10:27       ` Ludovic Courtès
2020-11-18 21:35         ` Ludovic Courtès [this message]
2020-10-24 22:58     ` Jan Nieuwenhuizen

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=87wnyijqkw.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=43920-done@debbugs.gnu.org \
    --cc=efraim@flashner.co.il \
    --cc=janneke@gnu.org \
    --cc=leo.prikler@student.tugraz.at \
    /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).