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: Emacs Package Management Date: Thu, 17 Sep 2009 08:24:09 -0600 Message-ID: References: <485b0c380808011427n4d3144eey3f8daf3abac83bf4@mail.gmail.com> <87d45vzt4j.fsf@hagelb.org> <87hbv20ybw.fsf@thinkpad.tsdh.de> <87d45p29zr.fsf@thinkpad.tsdh.de> Reply-To: Tom Tromey NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1253197477 1504 80.91.229.12 (17 Sep 2009 14:24:37 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 17 Sep 2009 14:24:37 +0000 (UTC) Cc: emacs-devel@gnu.org, rms@gnu.org, phil@hagelb.org To: joakim@verona.se Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Sep 17 16:24:30 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 1MoHuQ-0005ef-1r for ged-emacs-devel@m.gmane.org; Thu, 17 Sep 2009 16:24:30 +0200 Original-Received: from localhost ([127.0.0.1]:45188 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MoHuP-0003Yj-79 for ged-emacs-devel@m.gmane.org; Thu, 17 Sep 2009 10:24:29 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MoHuG-0003YS-M1 for emacs-devel@gnu.org; Thu, 17 Sep 2009 10:24:20 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MoHuB-0003YG-Q5 for emacs-devel@gnu.org; Thu, 17 Sep 2009 10:24:20 -0400 Original-Received: from [199.232.76.173] (port=37126 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MoHuB-0003YD-Lh for emacs-devel@gnu.org; Thu, 17 Sep 2009 10:24:15 -0400 Original-Received: from mx1.redhat.com ([209.132.183.28]:24114) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MoHu9-0006SN-8s; Thu, 17 Sep 2009 10:24:13 -0400 Original-Received: from int-mx04.intmail.prod.int.phx2.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com [10.5.11.17]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id n8HEOCeA006961; Thu, 17 Sep 2009 10:24:12 -0400 Original-Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx04.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id n8HEOAWr008490; Thu, 17 Sep 2009 10:24:10 -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 n8HEOAAS005273; Thu, 17 Sep 2009 10:24:10 -0400 Original-Received: by opsy.redhat.com (Postfix, from userid 500) id 0D39E3781CE; Thu, 17 Sep 2009 08:24:10 -0600 (MDT) X-Attribution: Tom In-Reply-To: <87d45p29zr.fsf@thinkpad.tsdh.de> (Tassilo Horn's message of "Thu, 17 Sep 2009 11:31:20 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) X-Scanned-By: MIMEDefang 2.67 on 10.5.11.17 X-detected-operating-system: by monty-python.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:115415 Archived-At: >>>>> "Tassilo" == Tassilo Horn writes: Tassilo> I don't think that's a good approach, because it requires a lot of Tassilo> maintenance and testing on the package repository side. It would be Tassilo> better if a package could specify something like Tassilo> (package "my-package" Tassilo> (version "1.0") Tassilo> (need ">=emacs-23")) It does do this. Take a look at package.el. Tassilo> (package "my-package" Tassilo> (version "0.8") Tassilo> (need ">=emacs-22.1" " So when I run emacs 22, package.el would show version 0.8 of Tassilo> my-package, with emacs 23 it would show version 1.0, and with Tassilo> emacs 21 it wouldn't be shown as not installable. I didn't do this, either. I think few people bounce between Emacs versions this way. Tassilo> Another issue is updating. There the question is: Can I update Tassilo> package A without breaking any other package that needs it? Yes. Assuming package A is backward compatible. package.el doesn't check this, it has no way to. Tom