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

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

[Donald Curtis]

I know there is a feature freeze but one of the most requested features (myself included) seems to be an "update" for packages in package.el.  

https://gist.github.com/1211655

(defun package-update-all ()
  "Update all packages"
  (interactive)
  (dolist (elt package-alist)
    (let* ((name (car elt))
           (file-name (symbol-name name))
           (available-pkg (assq name package-archive-contents))
           (available-version (and available-pkg
                                   (package-desc-vers (cdr available-pkg))))
           (current-version (package-desc-vers (cdr elt)))
           )
      (when (and available-version
                 (version-list-< current-version available-version))
        (message "Updating to: %s - %s" file-name
                 (package-version-join available-version))
        (package-install name)
        (package-delete file-name (package-version-join current-version))))))


At least this is available if anyone wants to just put it in their own init file.  It's probably not completely right as I am very new to programming this lisp stuff.

Thanks,
Donald

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

[Phil Hagelberg]

On Mon, Sep 12, 2011 at 9:32 AM, Donald Curtis <dcurtis@gmail.com> wrote:
> I know there is a feature freeze but one of the most requested features (myself included) seems to be an "update" for packages in package.el.

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?

-Phil

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

[Chong Yidong]

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.

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

[Chong Yidong]

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.