Open laurynas-biveinis opened 5 years ago
epm uses epl-outdated-packages
from https://github.com/cask/epl to get outdated packages which doesn't take account of package-archive-priorities
. According to my memory, package.el is mainly a user program and can't be easily programmatically operated (e.g., it doesn't provides an API which outputs the outdated packages)
I see that epl had this report: https://github.com/cask/epl/issues/32, which was closed because of https://github.com/cask/epl/pull/33, but it got closed without completing. Should I ask them to reopen https://github.com/cask/epl/issues/32?
I think so.
If .emacs/.epm.el is configured as follows:
Then Emacs does not try to upgrade melpa-stable packages to their melpa versions, and epm tries to. I.e. Emacs list-packages does not show any outdated packages, but epm outdated does:
I have checked by trying to upgrade some packages and I see a melpa-stable version being replaced with melpa one, i.e.:
I believe package-archive-priorities should be honored by epm too.
Thanks,