From: Seb <spluque@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: upgrading packages via script
Date: Wed, 27 Sep 2017 17:39:51 -0500 [thread overview]
Message-ID: <873777bwaw.fsf@gmail.com> (raw)
In-Reply-To: 878th0yx41.fsf@gmail.com
On Wed, 27 Sep 2017 10:33:50 -0500,
Seb <spluque@gmail.com> wrote:
> On Wed, 27 Sep 2017 15:21:26 +0200,
> Michael Heerdegen <michael_heerdegen@web.de> wrote:
>> Seb <spluque@gmail.com> writes:
>>> ╭───── [ upgrade_packages.el ] │ (setq package-archives │ (quote │
>>> (("gnu" . "http://elpa.gnu.org/packages/") │ ("melpa"
>>> . "http://melpa.org/packages/") │ ("marmalade"
>>> . "https://marmalade-repo.org/packages/") │ ("org"
>>> . "http://orgmode.org/elpa/")))) │ (package-initialize) │
>>> (list-packages) │ (package-menu-mark-upgrades) │
>>> (package-menu-execute t) ╰─────
>> My first guess would be that in nature, one has to wait until the
>> package manager has refreshed the view before one can select packages
>> to upgrade. Your script finishes before that because updating the
>> package list happens asynchronously.
> That was also my first guess, but in that case shouldn't
> (package-menu-execute t) fail altogether?
Well, I found the variable package-menu-async, which if toggled answers
my question. If set to nil in the script, then packages to upgrade are
found successfully against the latest candidates. If non-nil, as by
default, then things go wrong as shown, so answer is no.
And the working script boils down to:
╭───── [ upgrade_packages.el ]
│ (setq package-archives
│ (quote
│ (("gnu" . "http://elpa.gnu.org/packages/")
│ ("melpa" . "http://melpa.org/packages/")
│ ("marmalade" . "https://marmalade-repo.org/packages/")
│ ("org" . "http://orgmode.org/elpa/")))
│ package-menu-async nil)
│ (list-packages)
│ (package-menu-mark-upgrades)
│ (package-menu-execute t)
╰─────
--
Seb
next prev parent reply other threads:[~2017-09-27 22:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-26 14:55 upgrading packages via script Seb
2017-09-27 13:21 ` Michael Heerdegen
2017-09-27 15:33 ` Seb
2017-09-27 22:39 ` Seb [this message]
2017-09-27 14:21 ` Bastian Beischer
2017-09-27 15:31 ` Sebastian P. Luque
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=873777bwaw.fsf@gmail.com \
--to=spluque@gmail.com \
--cc=help-gnu-emacs@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.
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).