From: Stefan Kangas <stefankangas@gmail.com>
To: Visuwesh <visuweshm@gmail.com>, Lars Ingebrigtsen <larsi@gnus.org>
Cc: 48543@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>,
cpitclaudel@gmail.com, akrl@sdf.org
Subject: bug#48543: Feature request: put ELN cache in $XDG_CACHE_HOME by default
Date: Wed, 13 Jul 2022 07:01:50 -0700 [thread overview]
Message-ID: <CADwFkmmmXJi0b+voo8eXnL4wdf=LTZebo1K5QRgmf8rRUHfBZQ@mail.gmail.com> (raw)
In-Reply-To: <87y1wxgnwj.fsf@gmail.com>
Visuwesh <visuweshm@gmail.com> writes:
> Why not use XDG_DATA_HOME in that case?
I realize that the XDG Base Directory Specification could be more clear
on these details, but I believe that a study of the current practices as
well as previous discussions on e.g. the XDG mailing list, in Debian,
Arch and so on, would lead to the conclusion that this would be wrong.
It is generally understood that XDG_DATA_HOME is roughly analogus to
/usr/share and XDG_CACHE_HOME is roughly analogous to /var/cache -- one
is volatile, the other one is not.
For starters, please compare the contents of ~/.local/share with
~/.cache on your machine to see what other software puts where.
Next, to understand how these issues are often approached, I invite you
to study references such as:
https://wiki.debian.org/XDGBaseDirectorySpecification
https://wiki.archlinux.org/title/XDG_Base_Directory
https://wiki.gnome.org/action/show/Initiatives/GnomeGoals/XDGConfigFolders
https://bugzilla.mozilla.org/show_bug.cgi?id=259356
There are more to find obviously, but that should be plenty to get the
discussion started.
> It doesn't get cleared I think.
AFAIK, $XDG_CACHE_HOME also doesn't "get cleared" arbitrarily. There
has to be some action on behalf of the user for that to happen.
next prev parent reply other threads:[~2022-07-13 14:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-20 17:25 bug#48543: Feature request: put ELN cache in $XDG_CACHE_HOME by default Clément Pit-Claudel
2022-07-13 12:08 ` Lars Ingebrigtsen
2022-07-13 12:42 ` Eli Zaretskii
2022-07-13 12:45 ` Lars Ingebrigtsen
2022-07-13 13:09 ` Visuwesh
2022-07-13 14:01 ` Stefan Kangas [this message]
2022-07-13 13:40 ` Andrea Corallo
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='CADwFkmmmXJi0b+voo8eXnL4wdf=LTZebo1K5QRgmf8rRUHfBZQ@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=48543@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=cpitclaudel@gmail.com \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
--cc=visuweshm@gmail.com \
/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/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.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.