From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Achim Gratz Newsgroups: gmane.emacs.devel Subject: Re: Require Emacs >=24.3 for next Org versions? Date: Mon, 17 Aug 2015 07:24:11 +0200 Organization: Linux Private Site Message-ID: <87oai6lc78.fsf@Rainer.invalid> References: <87mvxtdjkn.fsf@gnu.org> <87pp2nkasy.fsf@Rainer.invalid> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1439789090 21771 80.91.229.3 (17 Aug 2015 05:24:50 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 17 Aug 2015 05:24:50 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Aug 17 07:24:41 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1ZRCuV-0002FD-SJ for ged-emacs-devel@m.gmane.org; Mon, 17 Aug 2015 07:24:40 +0200 Original-Received: from localhost ([::1]:54278 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZRCuV-0005WJ-89 for ged-emacs-devel@m.gmane.org; Mon, 17 Aug 2015 01:24:39 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:51647) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZRCuH-0005W7-PU for emacs-devel@gnu.org; Mon, 17 Aug 2015 01:24:27 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZRCuD-00007l-NK for emacs-devel@gnu.org; Mon, 17 Aug 2015 01:24:25 -0400 Original-Received: from plane.gmane.org ([80.91.229.3]:39002) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZRCuD-00006v-GU for emacs-devel@gnu.org; Mon, 17 Aug 2015 01:24:21 -0400 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1ZRCu9-00023Z-Mx for emacs-devel@gnu.org; Mon, 17 Aug 2015 07:24:17 +0200 Original-Received: from p54b7e0f3.dip0.t-ipconnect.de ([84.183.224.243]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 17 Aug 2015 07:24:17 +0200 Original-Received: from Stromeko by p54b7e0f3.dip0.t-ipconnect.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 17 Aug 2015 07:24:17 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 41 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: p54b7e0f3.dip0.t-ipconnect.de User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux) Cancel-Lock: sha1:BcNAkTWcEWgWC5e4WAjkpsiv/9Y= X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:188831 Archived-At: Artur Malabarba writes: >> Now, even if we did keep an Emacs 23 compatible Org around (most likely >> being feature frozen and only getting critical bugfixes) we'd still have >> to solve the problem that Emacs' package manager currently can't serve >> different packages for different versions of Emacs. > > Emacs 23 didn't come with package.el, which means you're targetting > people who have manually added package.el to their system. I think > it's safe to assume that this group of people is capable of manually > downloading and setting up your compatibility org version. Just make > sure it's very visible and easy to find when searched for. For someone savvy enough wanting to install a newer Org on Emacs 23 I expect a good proportion to recognize also that installing package manager for Emacs 23 first is a good way to also update the other eLisp they have on their systems. However, that's not the issue I was commenting about. The issue, which admittedly doesn't really have much to do with Org and was meant as a side remark, still stands that package manager can't install different packages or package versions for different Emacs versions. If you wanted to do that, you'd need to create an ELPA archive for each version of Emacs and teach people to use the right one for the version they currently use. That strikes me as odd. At least the last part could be solved by optionally having a version-specific sub-structure in ELPA and have Emacs' package manager look there first. I tend to the idea that each such sub-structure should be a complete package archive, based on the assumption that it would be served from a system that knows about (hard-)links or virtual directories (that is the webserver rewrites the request to use some other directory if it can't find it in the one you were looking). Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Factory and User Sound Singles for Waldorf rackAttack: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds