bug#19390: 25.0.50; `package-activate' is too slow

[Artur Malabarba]

I see what you meant now. The RELOAD argument should not be passed to
package-activate-1 when activating dependencies. That should fix the
issue.

The dependency will already have been reloaded when (if) it was upgraded.

2014-12-18 12:47 GMT-02:00 Dmitry Gutov <dgutov@yandex.ru>:
> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>
>>> Aside from it, if we compare with the alternative implementation
>>> suggestions, the current one reloads all dependencies, even those that
>>> haven't been (re)installed during the current session.
>>
>> It sounds serious, but I don't understand what you're referring to.
>> Can you give an example?
>
> It reloads all dependencies of the package that is currently being
> installed.
>
> Try this:
>
> (advice-add 'package-activate-1 :before
>             (lambda (pkg-desc &optional reload)
>               (message "package-activate-1 called with %s %s"
>                        (package-desc-name pkg-desc) reload))
>             '((name . "Parrot arguments")))
>
> Then install company (if your haven't yet), and then, with Melpa in
> package archives, install company-math. You'll see this in *Messages*:
>
> package-activate-1 called with company force
> package-activate-1 called with math-symbol-lists force
> package-activate-1 called with company-math force