unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Cc: Lars Ingebrigtsen <larsi@gnus.org>
Subject: Re: master feb654b460: Add new package.el commands for recompilation
Date: Thu, 16 Jun 2022 08:22:27 -0400	[thread overview]
Message-ID: <jwv4k0kztno.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <20220616114917.A93A0C051C9@vcs2.savannah.gnu.org> (Lars Ingebrigtsen's message of "Thu, 16 Jun 2022 07:49:17 -0400 (EDT)")

> +;;;###autoload
> +(defun package-recompile (pkg)
> +  "Byte-compile package PKG again.
> +PKG should be either a symbol, the package name, or a `package-desc'
> +object."
> +  (interactive (list (intern (completing-read
> +                              "Recompile package: "
> +                              (mapcar #'symbol-name
> +                                      (mapcar #'car package-alist))))))
> +  (let ((pkg-desc (if (package-desc-p pkg)
> +                      pkg
> +                    (cadr (assq pkg package-alist)))))
> +    ;; Delete the old .elc files to ensure that we don't inadvertently
> +    ;; load them (in case they contain byte code/macros that are now
> +    ;; invalid).
> +    (dolist (elc (directory-files (package-desc-dir pkg-desc) t "\\.elc\\'"))
> +      (delete-file elc))
> +    (package--compile pkg-desc)))

Thanks, Lars.  But note that there are packages with ELisp files in
subdirectories (Hyperbole and Proof-General come to mind, tho I'm sure
there are others) so we should work a bit harder than the above
`directory-files`.


        Stefan




       reply	other threads:[~2022-06-16 12:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <165538015737.18417.15587779043841057948@vcs2.savannah.gnu.org>
     [not found] ` <20220616114917.A93A0C051C9@vcs2.savannah.gnu.org>
2022-06-16 12:22   ` Stefan Monnier [this message]
2022-06-16 12:26     ` master feb654b460: Add new package.el commands for recompilation Lars Ingebrigtsen
2022-06-23 15:53     ` Lynn Winebarger

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=jwv4k0kztno.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.org \
    /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).