From mboxrd@z Thu Jan 1 00:00:00 1970 From: Achim Gratz Subject: Re: ELPA Date: Tue, 28 Sep 2010 20:59:53 +0200 Message-ID: <87iq1plmmu.fsf@Rainer.invalid> References: <87tylcy6gw.fsf@stats.ox.ac.uk> <87hbhc5rtt.fsf@Rainer.invalid> <87r5ggs6u6.fsf@stats.ox.ac.uk> <87tylce24o.fsf@Rainer.invalid> <87iq1srzoj.fsf_-_@stats.ox.ac.uk> <87eicdiwsy.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from [140.186.70.92] (port=57953 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1P0fPM-0003bn-3R for emacs-orgmode@gnu.org; Tue, 28 Sep 2010 15:00:09 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1P0fPK-0000Tm-Dc for emacs-orgmode@gnu.org; Tue, 28 Sep 2010 15:00:07 -0400 Received: from lo.gmane.org ([80.91.229.12]:35828) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1P0fPK-0000Tb-2x for emacs-orgmode@gnu.org; Tue, 28 Sep 2010 15:00:06 -0400 Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1P0fPG-0005te-R7 for emacs-orgmode@gnu.org; Tue, 28 Sep 2010 21:00:02 +0200 Received: from p57aaceec.dip.t-dialin.net ([87.170.206.236]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 28 Sep 2010 21:00:02 +0200 Received: from Stromeko by p57aaceec.dip.t-dialin.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 28 Sep 2010 21:00:02 +0200 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org "Eric Schulte" writes: > I would think that it only makes sense to have one Org-mode package in > ELPA, namely the bleeding edge git version of Org-mode. I disagree and my vote is still on 'maint', i.e. what a user would be most likely to install if he was visiting orgmode.org. Master changes too often and might have experimental commits that later get reversed. For anybody not following the mailing list this would be exactly the wrong version to get through ELPA, especially since ELPA (at least in standard configuration) does not notify about new versions. > ELPA serves as a way to distribute packages which are not (or can't > be) part of Emacs, This is true of the current ELPA (tromey.com), but I feel the GNU ELPA might take on an additional role: 1) easily obtaining packages that would not normally come with the standard install of Emacs and 2) keeping users updated on packages that are still developed and change between releases. Org-mode would fall into the second category since it will probably stay in the standard package set. > Also, I would tend to think that this would make the most sense if we > automate the ELPA integration s.t. every time a new revision is pushed > up the to git repository, the ELPA version is automatically upgraded > (with a git commit hook). If this isn't currently possible in ELPA then > I'd agree with a point Jambunathan makes in this thread that this is a > trick we can help ELPA to learn. Again, Emacs24 ELPA will be able to query multiple archives, something that current ELPA can't. So Emacs24 will by default look at elpa.gnu.org and users should be able to find the latest stable version there (it may not show up exactly in the minute it is released on orgmode.org). It should then be easy enough to configure ELPA (from org-mode even?) to look for updates on orgmode.org first and get bleeding edge from there if the user asks to do this. If GNU ELPA adopts a different package update policy then both the stable and bleeding edge version would need to be on orgmode.org -- has anybody had a chance to ask or followed the discussion on the emacs.devel list? Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptation for Waldorf microQ V2.22R2: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada