unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: pkg-autoloads.el vs. pkg-loaddefs.el
Date: Tue, 18 Jun 2024 16:00:02 +0000	[thread overview]
Message-ID: <871q4us0l9.fsf@localhost> (raw)
In-Reply-To: <jwvfrtbfzez.fsf-monnier+emacs@gnu.org>

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

>> It means that built-in org-loaddefs.el version pre-loaded with Emacs
>> remains active and any changes in org-loaddefs.el in ELPA Org mode
>> vs. built-in Org mode are not updated.
>
> `org-loaddefs.el` shouldn't be any different from any other `org*.el`
> file, in this respect: if it's been loaded before the package is
> activated, then (hopefully) `package--reload-previously-loaded` should
> reload the newer file.
>
> [ I've heard various reports over the years that indicate that
>   `package--reload-previously-loaded` doesn't always do that, but
>   I don't know if it's because it's not called at all, or because it's
>   called but makes wrong decisions.
>   Also of course, there can be lots of cases where reloading a file isn't
>   sufficient. ]

But isn't it called only when `package-activate-1' is called with RELOAD
argument? AFAIU, `package-activate' (and thus `package-activate-all')
calls (package-activate-1 pkg-desc nil 'deps).

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>



  reply	other threads:[~2024-06-18 16:00 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-20 12:56 pkg-autoloads.el vs. pkg-loaddefs.el Ihor Radchenko
2024-06-14 13:54 ` Stefan Monnier via Emacs development discussions.
2024-06-17 13:45   ` Ihor Radchenko
2024-06-17 14:04     ` Stefan Monnier
2024-06-18 16:00       ` Ihor Radchenko [this message]
2024-06-18 17:23         ` Stefan Monnier
2024-06-18 17:39           ` Ihor Radchenko
2024-06-18 19:43             ` Stefan Monnier
2024-06-18 20:03               ` Ihor Radchenko
2024-06-18 20:12                 ` Stefan Monnier
2024-06-19 15:32                   ` Ihor Radchenko
2024-06-19 15:58                     ` Stefan Monnier
2024-06-19 16:22                       ` Ihor Radchenko
2024-06-19 20:35                         ` Stefan Monnier
2024-06-20  5:01                           ` Eli Zaretskii
2024-07-28 13:52                             ` Ihor Radchenko
2024-08-14  0:31                               ` Stefan Monnier
2024-08-14  5:43                                 ` Eli Zaretskii
2024-06-20 15:33                           ` Ihor Radchenko

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=871q4us0l9.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).