From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Emacs Package Management Date: Thu, 01 Oct 2009 01:01:58 -0400 Message-ID: References: <485b0c380808011427n4d3144eey3f8daf3abac83bf4@mail.gmail.com> <87ej589vku.fsf@hagelb.org> <485b0c380808050609y56042595l42a5bb05b34458f0@mail.gmail.com> <485b0c380909161536t331a71fdg1c45150c418b72b2@mail.gmail.com> <87ab0eai3l.fsf@hagelb.org> <87eipqpwfi.fsf@stupidchicken.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1254373346 7469 80.91.229.12 (1 Oct 2009 05:02:26 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 1 Oct 2009 05:02:26 +0000 (UTC) Cc: Chong Yidong , emacs-devel@gnu.org, rms@gnu.org, spedrosa@gmail.com, phil@hagelb.org To: Tom Tromey Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Oct 01 07:02:19 2009 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.50) id 1MtDo2-00034B-36 for ged-emacs-devel@m.gmane.org; Thu, 01 Oct 2009 07:02:18 +0200 Original-Received: from localhost ([127.0.0.1]:35468 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MtDo1-0008VT-Gt for ged-emacs-devel@m.gmane.org; Thu, 01 Oct 2009 01:02:17 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MtDnt-0008VI-Nl for emacs-devel@gnu.org; Thu, 01 Oct 2009 01:02:09 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MtDno-0008U4-UR for emacs-devel@gnu.org; Thu, 01 Oct 2009 01:02:09 -0400 Original-Received: from [199.232.76.173] (port=56835 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MtDno-0008Tz-QB for emacs-devel@gnu.org; Thu, 01 Oct 2009 01:02:04 -0400 Original-Received: from mx20.gnu.org ([199.232.41.8]:16767) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MtDnl-0007zq-C6; Thu, 01 Oct 2009 01:02:01 -0400 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.181] helo=ironport2-out.pppoe.ca) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MtDnk-0004wl-T4; Thu, 01 Oct 2009 01:02:00 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AtoEADzUw0pMCrXH/2dsb2JhbACBUdRehCgEhxI X-IronPort-AV: E=Sophos;i="4.44,484,1249272000"; d="scan'208";a="46883675" Original-Received: from 76-10-181-199.dsl.teksavvy.com (HELO pastel.home) ([76.10.181.199]) by ironport2-out.pppoe.ca with ESMTP; 01 Oct 2009 01:01:58 -0400 Original-Received: by pastel.home (Postfix, from userid 20848) id 912588109; Thu, 1 Oct 2009 01:01:58 -0400 (EDT) In-Reply-To: (Tom Tromey's message of "Wed, 30 Sep 2009 14:18:56 -0600") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.50 (gnu/linux) X-detected-operating-system: by mx20.gnu.org: Genre and OS details not recognized. X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6, seldom 2.4 (older, 4) 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:115818 Archived-At: Stefan> In order to move forward on this thing, here's what I'd like to Stefan> have as a first step: the equivalent of `dpkg', i.e. an elisp Stefan> package that can take a package (a tarball, most likely) and Stefan> "install it", list the set of installed packages, uninstall Stefan> a package. > I was thinking more about integrating package.el and I remembered one > problem. > Right now, package.el byte-compiles at install time. However, this > yields incorrect results if the .elc format changes incompatibly, and > the user upgrades Emacs. I believe this has happened in the past. We normally try to preserve forward compatibility, so old .elcs should work fine. IOW, the problem can only show up if the user byte-compiles with the new Emacs and then uses the file with an older Emacs. If that's the problem, then I wouldn't worry about it (after all, the same happens already for the normal manual installation procedure or external packages). > We discussed a solution to this long ago: putting the .elc files into a > shadow directory hierarchy. Is this still a good idea? If possible, I'd rather avoid the complexity. Stefan