Re: pkg-autoloads.el vs. pkg-loaddefs.el

[Ihor Radchenko <yantar92@posteo.net>]

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>