From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Tom Tromey Newsgroups: gmane.emacs.devel Subject: Re: document package.el Date: Fri, 27 Aug 2010 09:51:36 -0600 Message-ID: References: <4C5CBA32.9000109@gmail.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: dough.gmane.org 1282925228 11508 80.91.229.12 (27 Aug 2010 16:07:08 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Fri, 27 Aug 2010 16:07:08 +0000 (UTC) Cc: emacs-devel@gnu.org To: Uday S Reddy Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Aug 27 18:07:07 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 1Op1SE-0007JZ-99 for ged-emacs-devel@m.gmane.org; Fri, 27 Aug 2010 18:07:06 +0200 Original-Received: from localhost ([127.0.0.1]:37925 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Op1SB-00076X-QB for ged-emacs-devel@m.gmane.org; Fri, 27 Aug 2010 12:06:55 -0400 Original-Received: from [140.186.70.92] (port=47499 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Op1GP-0002K4-C2 for emacs-devel@gnu.org; Fri, 27 Aug 2010 11:56:25 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1Op1DY-0001Hf-1v for emacs-devel@gnu.org; Fri, 27 Aug 2010 11:54:11 -0400 Original-Received: from mx1.redhat.com ([209.132.183.28]:54422) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1Op1DX-0001HB-Rm for emacs-devel@gnu.org; Fri, 27 Aug 2010 11:51:48 -0400 Original-Received: from int-mx03.intmail.prod.int.phx2.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.16]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id o7RFpclv029539 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 27 Aug 2010 11:51:38 -0400 Original-Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx03.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id o7RFpc8R011861; Fri, 27 Aug 2010 11:51:38 -0400 Original-Received: from opsy.redhat.com (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id o7RFpakc012592; Fri, 27 Aug 2010 11:51:37 -0400 Original-Received: by opsy.redhat.com (Postfix, from userid 500) id BF682378883; Fri, 27 Aug 2010 09:51:36 -0600 (MDT) X-Attribution: Tom In-Reply-To: (Uday S. Reddy's message of "Fri, 27 Aug 2010 07:43:17 +0100") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux) X-Scanned-By: MIMEDefang 2.67 on 10.5.11.16 X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. 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:129311 Archived-At: >>>>> "Uday" == Uday S Reddy writes: Uday> I personally think that upgrading packages should be a conscious, Uday> deliberate action. You never know what changes the developers have Uday> put in the upgrade and what those change would entail in terms of how Uday> you will use the package. This is exactly why I didn't write package.el to work automatically :-) It should be implementable, though, if somebody really wants it. Another idea would be to do what Mozilla's plugin manager does: look for updates in the background, and notify the users of possible upgrades. Uday> I will also want to install the new versions along side the old ones, Uday> so that I have the option of going back to the old versions if I need Uday> to. It is not yet clear to me if package.el allows that. If you install a new version the old one will still be there. You have to explicitly delete it. So, you can go back to an older one by deleting the newer one. This isn't foolproof because installing a new version of a package may install new versions of its dependencies, and there's no easy way (without reading through files in ~/.emacs.d/elpa/) to know what those are after the fact. Tom