all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
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: Thu, 16 Jun 2022 13:50:48 +0200	[thread overview]
Message-ID: <87r13oesiv.fsf@gnus.org> (raw)
In-Reply-To: <jwvk09hvoiq.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Wed, 15 Jun 2022 13:18:29 -0400")

Stefan Monnier <monnier@iro.umontreal.ca> writes:

> There should be a command/function to recompile an installed package,
> and maybe another to do the same for all packages, yes.

OK; I've now added two commands for that to Emacs 29.

> 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.

I'm not sure there's any way of doing that that would be reliable enough
not to be annoying?  That is, we can determine if an .elc file is
readable, but we can't really detect if it's using a macro that has
changed so much that the .elc file should be rebuilt...

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      reply	other threads:[~2022-06-16 11:50 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
2022-06-16 11:50       ` Lars Ingebrigtsen [this message]

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=87r13oesiv.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=27253@debbugs.gnu.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.