From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: "N. Jackson" <nljlistbox2@gmail.com>, 27253@debbugs.gnu.org
Subject: bug#27253: 25.2; Suggestion: On startup after Emacs version change, package should offer to correct invalid bytecode
Date: Wed, 15 Jun 2022 13:18:29 -0400 [thread overview]
Message-ID: <jwvk09hvoiq.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87letxg9li.fsf@gnus.org> (Lars Ingebrigtsen's message of "Wed, 15 Jun 2022 18:44:25 +0200")
Lars Ingebrigtsen [2022-06-15 18:44:25] wrote:
> Lars Ingebrigtsen <larsi@gnus.org> writes:
>> There should perhaps be a command to recompile all installed packages?
>> Or does that exist somewhere? (I don't see any such command...)
> Perhaps Stefan knows; added to the CCs.
There should be a command/function to recompile an installed package,
and maybe another to do the same for all packages, yes.
I don't think the OP's situation would be best served by recompiling
everything, because usually recompilation is only needed for those few
packages that were compiled a *long* time ago ( where I'd expect most
packages have probably been recompiled since then because of
package updates).
But there's definitely room for improvement along the path of:
detecting the presence of a file that's too old, figuring out which
package needs to be recompiled, and then recompiling it.
Stefan
next prev parent reply other threads:[~2022-06-15 17:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-05 15:19 bug#27253: 25.2; Suggestion: On startup after Emacs version change, package should offer to correct invalid bytecode N. Jackson
2022-05-17 19:08 ` Lars Ingebrigtsen
2022-06-15 16:44 ` Lars Ingebrigtsen
2022-06-15 17:18 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-06-16 11:50 ` Lars Ingebrigtsen
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=jwvk09hvoiq.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=27253@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
--cc=nljlistbox2@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.