From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Christoph Newsgroups: gmane.emacs.devel Subject: Re: document package.el Date: Fri, 27 Aug 2010 16:58:33 -0600 Message-ID: <4C784319.4050807@gmail.com> References: <4C5CBA32.9000109@gmail.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Trace: dough.gmane.org 1282949939 4244 80.91.229.12 (27 Aug 2010 22:58:59 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Fri, 27 Aug 2010 22:58:59 +0000 (UTC) Cc: u.s.reddy@cs.bham.ac.uk, rms@gnu.org To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Aug 28 00:58:58 2010 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Op7st-0006MQ-LV for ged-emacs-devel@m.gmane.org; Sat, 28 Aug 2010 00:58:55 +0200 Original-Received: from localhost ([127.0.0.1]:56844 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Op7st-0006nk-6x for ged-emacs-devel@m.gmane.org; Fri, 27 Aug 2010 18:58:55 -0400 Original-Received: from [140.186.70.92] (port=56543 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Op7sj-0006nU-I1 for emacs-devel@gnu.org; Fri, 27 Aug 2010 18:58:50 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1Op7se-0006Gr-8v for emacs-devel@gnu.org; Fri, 27 Aug 2010 18:58:45 -0400 Original-Received: from mail-gx0-f169.google.com ([209.85.161.169]:53836) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1Op7se-0006Gk-64; Fri, 27 Aug 2010 18:58:40 -0400 Original-Received: by gxk9 with SMTP id 9so1821958gxk.0 for ; Fri, 27 Aug 2010 15:58:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=O4YeHSK9LgTTMYzlCN/EYZNjzL0HFezmXz/dzWVBQCQ=; b=YNuksLcJBp1sGwY+lVlJX6XOItw2bFtTPk5XXFnYFDTR0yvftlRlsLbTAifj3KIgjT 1AI8n2DvxfTqeBmSldeGIoWq10LR0iXg6SoxeIt3ZYWtiUJ7cjyO5VYXR0j5yTxWsyqE avN94QRmrhqjBjL+VOTusdvGrjUS/gmF8lypQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=sxbuFeny2xaRe8ZEcINQUoh4CVFn+8WVCRAQcnY0h1WrHLSei1nWlwoSxV75X999Ba 1qHgf0TFQza5SRRX7kZ+Opu0pWgDxLGy6s36z96e064vgB0sTcZn6BRu+9ezBSVA3Nph yv0gYp1Gpf8qgE0JUcUa8vC52XF7E3e0s6qOw= Original-Received: by 10.100.232.8 with SMTP id e8mr1680705anh.42.1282949919341; Fri, 27 Aug 2010 15:58:39 -0700 (PDT) Original-Received: from [192.168.1.3] (174-16-113-74.hlrn.qwest.net [174.16.113.74]) by mx.google.com with ESMTPS id h5sm7032133anb.8.2010.08.27.15.58.37 (version=SSLv3 cipher=RC4-MD5); Fri, 27 Aug 2010 15:58:38 -0700 (PDT) User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2 In-Reply-To: X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:129322 Archived-At: 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