From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: 48108@debbugs.gnu.org, akrl@sdf.org
Subject: bug#48108: Wishlist: Command to remove redundant eln cache directories [native-comp]
Date: Fri, 30 Apr 2021 10:59:37 +0300 [thread overview]
Message-ID: <838s50cidy.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmm-wxs_HLbK+OfFSL7MiZs4YvJdf6qz8HcwGVHviUjK2Q@mail.gmail.com> (message from Stefan Kangas on Thu, 29 Apr 2021 16:59:44 -0500)
> From: Stefan Kangas <stefan@marxist.se>
> Date: Thu, 29 Apr 2021 16:59:44 -0500
> Cc: Andrea Corallo <akrl@sdf.org>
>
> 1. Remove cache directories for versions older than the version
> specified by a new user option that defaults to
> (- emacs-major-version 2) or something.
>
> Remove cache directories for the same version as the current one
> but with a different hash.
>
> Remove duplicate directories for any given version, except the
> most recently added one.
>
> 2. Remove all eln cache directories except the one currently in use.
This is somewhat tricky, so I suggest that you (or someone else) comes
up with a convenient UI for such a feature and describes it in enough
detail to see whether it's feasible. Namely, how would the user
indicate which *.eln files can be deleted and which should stay?
Some thought points:
. the .eln hashes depend not only on the version but also on other
internal details, like the ABI version and more
. it isn't clear how the user will be able to come up with "the
hash" (especially since there are several hashes involved, not
just one)
> I imagine that casual users only ever use one version of Emacs at the
> same time (i.e. because they simply install Emacs using their package
> manager), so perhaps the first one could be the default mode of
> operation.
I don't know what you mean by "casual users", but I generally have all
the versions since Emacs 21 installed on my machines.
Btw, we might go look what others do with similar caches, for example
Guile. Do they even bother to clean these caches up?
next prev parent reply other threads:[~2021-04-30 7:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-29 21:59 bug#48108: Wishlist: Command to remove redundant eln cache directories [native-comp] Stefan Kangas
2021-04-30 7:59 ` Eli Zaretskii [this message]
2022-07-01 11:11 ` Lars Ingebrigtsen
2022-07-01 11:36 ` Eli Zaretskii
2022-07-01 16:18 ` Rudolf Schlatte
2022-07-01 18:13 ` Eli Zaretskii
2022-07-02 10:40 ` Lars Ingebrigtsen
2022-07-02 10:48 ` Eli Zaretskii
2022-07-02 11:01 ` Lars Ingebrigtsen
[not found] <CAAeL0SRmG9KtR7PLcmYrS2DUsiuWz72stWz=ir5F02rZnLfJ3A@mail.gmail.com>
2022-11-28 12:44 ` Eli Zaretskii
2022-11-28 13:09 ` Juanma Barranquero
2022-11-28 13:22 ` Juanma Barranquero
2022-11-28 13:43 ` Eli Zaretskii
2022-11-28 13:54 ` Juanma Barranquero
2022-11-28 14:44 ` Eli Zaretskii
2022-11-28 15:14 ` Juanma Barranquero
2022-11-28 16:48 ` Eli Zaretskii
2022-11-28 16:53 ` Juanma Barranquero
2022-11-28 13:38 ` Eli Zaretskii
2022-11-28 13:48 ` Juanma Barranquero
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=838s50cidy.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=48108@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=stefan@marxist.se \
/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/emacs.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).