From: Christoph <cschol2112@googlemail.com>
To: emacs-devel@gnu.org
Cc: u.s.reddy@cs.bham.ac.uk, rms@gnu.org
Subject: Re: document package.el
Date: Fri, 27 Aug 2010 16:58:33 -0600 [thread overview]
Message-ID: <4C784319.4050807@gmail.com> (raw)
In-Reply-To: <E1Op6hS-00056A-OZ@fencepost.gnu.org>
On 8/27/2010 3:43 PM, Richard Stallman wrote:
> I personally think that upgrading packages should be a conscious, deliberate
> action. You never know what changes the developers have put in the upgrade and
> what those change would entail in terms of how you will use the package.
>
> I agree. Not only that, but we want users to be conscious of and control
> what software they run. Leading them to let things be updated automatically
> is the opposite of that.
Agreed, but like Tom said, there could (and imho should) be an option to
check for updates of specified packages on startup or periodically and
provide an "update available" notification to the user.
Options could be
- Check manually
- Check on startup
- Check in a user-specified interval (once per day, week, month)
- Check on startup and periodically
If updates are available, a list of packages with updates should be
presented to the user, where he can mark the packages he would like to
upgrade.
On a new installation this would also work and result in the latest
version of all specified packages being installed. With user
confirmation of course.
That's what I was initially looking for.
Christoph
next prev parent reply other threads:[~2010-08-27 22:58 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-06 22:42 document package.el Tom Tromey
2010-08-06 23:48 ` Phil Hagelberg
2010-08-09 16:22 ` Tom Tromey
2010-08-07 1:43 ` Christoph
2010-08-07 8:57 ` Geralt
2010-08-09 16:23 ` Tom Tromey
2010-08-26 23:27 ` Juri Linkov
2010-08-26 23:50 ` Stefan Monnier
2010-08-27 3:14 ` Christoph
2010-08-27 5:51 ` Uday S Reddy
2010-08-27 3:12 ` Christoph
2010-08-27 7:07 ` Uday S Reddy
2010-08-27 21:40 ` Phil Hagelberg
2010-08-28 17:34 ` Tom Tromey
2010-08-27 6:43 ` Uday S Reddy
2010-08-27 15:51 ` Tom Tromey
2010-08-27 16:17 ` Chong Yidong
2010-08-27 21:43 ` Richard Stallman
2010-08-27 22:58 ` Christoph [this message]
2010-08-28 7:25 ` Uday S Reddy
2010-08-07 7:47 ` Eli Zaretskii
2010-08-08 22:39 ` Chong Yidong
2010-08-09 16:24 ` Tom Tromey
2010-08-21 18:22 ` Tom Tromey
2010-08-21 18:51 ` Eli Zaretskii
2010-08-22 1:40 ` Tom Tromey
2010-08-08 23:06 ` Chong Yidong
2010-08-09 21:13 ` Tom Tromey
2010-08-21 18:37 ` Tom Tromey
2010-08-25 17:24 ` Chong Yidong
2010-08-25 17:34 ` Tom Tromey
2010-08-25 17:35 ` Chong Yidong
2010-08-17 14:37 ` Uday S Reddy
2010-08-17 15:57 ` Tom Tromey
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C784319.4050807@gmail.com \
--to=cschol2112@googlemail.com \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
--cc=u.s.reddy@cs.bham.ac.uk \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.