Re: First attempt at package-update-all for package.el

[Chong Yidong <cyd@stupidchicken.com>]

Chong Yidong <cyd@stupidchicken.com> writes:

> Phil Hagelberg <phil@hagelb.org> writes:
>
>> For the record, this is a commonly-requested feature where people ask
>> "why doesn't it do this?" and the response is generally "I dunno, but
>> it shouldn't be hard to implement; why don't you try?" =)
>>
>> Would be great to get this in once the feature freeze has melted.
>> What's the procedure for handling patches in this situation? Just ask
>> the author to re-submit after the release?
>
> I've discussed with Stefan, and we agree that it's important to have
> something like this in 24.1.  I'll take care of it shortly.

OK, I've committed a package-menu-mark-upgrades command to the Package
Menu, bound to U.  This places the appropriate flags for upgrading
packages that can be upgraded.  M-x list-packages also issues a message
if any packages can be upgraded.

As for a M-x package-upgrade-all command, I'm not sure yet.  The code
written by OP is on the right track, but it also needs some additional
machinery for displaying what packages are going to be upgraded
(possibly using a Package Menu buffer?) and prompting the user.