From: "Ludovic Courtès" <ludo@gnu.org>
To: Leo Prikler <leo.prikler@student.tugraz.at>
Cc: "Jan \(janneke\) Nieuwenhuizen" <janneke@gnu.org>,
43920@debbugs.gnu.org, Efraim Flashner <efraim@flashner.co.il>
Subject: [bug#43920] [SHEPHERD PATCH] shepherd: Move log file to XDG_CACHE_DIR.
Date: Sat, 24 Oct 2020 18:15:33 +0200 [thread overview]
Message-ID: <87h7qjiore.fsf@gnu.org> (raw)
In-Reply-To: <bbe34857052850f4ee224602320079d38eb837b6.camel@student.tugraz.at> (Leo Prikler's message of "Sat, 24 Oct 2020 00:17:22 +0200")
Hi,
Leo Prikler <leo.prikler@student.tugraz.at> skribis:
>> 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.
> That is actually not part of the XDG specification – it merely states,
> that non-essential files be put there. Whether or not one considers
> the shepherd log essential is debatable.
Right, that’s my interpretation of what “cache” means.
> You could alternatively put it under $XDG_DATA_HOME. Some projects
> like Xorg seem to do that. Of course, there always remains the option
> of having yet another environment variable or command line parameter
> for the placement of the log file.
Yup, XDG_DATA_HOME would work for me; it seems to be rather in line with
what the XDG states and what Xorg does, as you note.
https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html
WDYT, Efraim & Janneke?
Ludo’.
next prev parent reply other threads:[~2020-10-24 16:16 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 [this message]
2020-10-24 16:51 ` Efraim Flashner
2020-10-26 10:27 ` Ludovic Courtès
2020-11-18 21:35 ` bug#43920: " Ludovic Courtès
2020-10-24 22:58 ` [bug#43920] " 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=87h7qjiore.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=43920@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).