unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Qiantan Hong <qthong@stanford.edu>
To: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: PACKAGE-FEATURES, and hot update of Emacs packages
Date: Sat, 27 Nov 2021 09:31:10 +0000	[thread overview]
Message-ID: <5C502136-57BD-40D4-A1E8-A4313AD7CDFC@stanford.edu> (raw)

package-reinstall seems to update the external UNIX file system only,
and don’t update the package loaded in the Elisp image properly.
I didn’t find a built-in way to do so, which sucks because one need
to restart Emacs (and lost the image state) to update packages.

It turns out that Emacs seems to have almost all the necessary facility
to make hot update happens, the only missing one
seems to be package-features (that finds out features loaded from the package).
Then to really update p, one just need to

(mapc (lambda (feature) (unload-feature feature t)) (package-features p))
(package-reinstall p)
(require p)

(assuming p is the same as the “entry” feature of the whole package)

Currently I use an adhoc version
(defun package-features (p)
  (cl-remove-if-not
   (lambda (feature)
     (s-prefix-p (symbol-name p) (symbol-name feature)))
   features))

It works pretty well, I’m able to update all of my everyday packages successfully,
which shows that hot update is very doable. Now for the rare case
that the default behavior result in inconsistent state, package maintainer
can always define feature-UNLOAD-FUNCTION to make it work nicely.

Now back to the only missing pieces, how much effort it’d take to have
a proper PACKAGE-FEATURES? Is it good to have it in core? 
(I suppose it’d be a minor change to package.el).

Best,
Qiantan




             reply	other threads:[~2021-11-27  9:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-27  9:31 Qiantan Hong [this message]
2021-11-27 10:09 ` PACKAGE-FEATURES, and hot update of Emacs packages Eli Zaretskii
2021-11-27 10:18   ` Qiantan Hong
2021-11-27 10:20     ` Qiantan Hong
2021-11-27 12:16 ` Phil Sainty
2021-11-27 13:30   ` Phil Sainty
2021-11-27 20:36   ` Qiantan Hong
2021-11-28  7:22     ` Phil Sainty
2021-11-28  7:51       ` Qiantan Hong
2021-11-28  1:04   ` Tim Cross
2021-11-28  4:23     ` Phil Sainty
2021-11-28  5:12     ` Stefan Monnier

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=5C502136-57BD-40D4-A1E8-A4313AD7CDFC@stanford.edu \
    --to=qthong@stanford.edu \
    --cc=emacs-devel@gnu.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).