From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stefan Monnier Subject: Re: Sync up the org in emacs master to org maint branch? Date: Thu, 02 Feb 2017 13:17:05 -0500 Message-ID: References: <87k29d7zvw.fsf@engster.org> <87fuk08i01.fsf@engster.org> <87d1f36xnc.fsf@engster.org> <87a8a4ees0.fsf@engster.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:33905) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cZLwi-0006IB-Jf for emacs-orgmode@gnu.org; Thu, 02 Feb 2017 13:17:25 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cZLwf-0004bN-Ch for emacs-orgmode@gnu.org; Thu, 02 Feb 2017 13:17:24 -0500 Received: from [195.159.176.226] (port=52039 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cZLwf-0004at-6E for emacs-orgmode@gnu.org; Thu, 02 Feb 2017 13:17:21 -0500 Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1cZLwV-0002od-Gz for emacs-orgmode@gnu.org; Thu, 02 Feb 2017 19:17:11 +0100 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: emacs-orgmode@gnu.org Cc: emacs-devel@gnu.org > So let me try again: What I find completely misguided is to move > packages out of core *but still putting them into the release*. In other > words, in my opinion there are really just two options that make sense: > you either keep a package in core, or you kick it out and don't ship it > with the release. AFAIK I am the one who started with the idea of including ELPA packages in the tarball, so I feel like I have to answer here: The idea was not to push packages out to elpa.git only to then include them in the tarball. Instead, the idea was just to allow some packages into the tarball without having to move them from elpa.git to emacs.git. Their inclusion in the tarball is simply a way to make that package more widely available. E.g., I'd like to include company-mode in Emacs's tarball since this kind of completion is very popular (and also because I think Emacs as a whole suffers from the dilution of effort between company-mode and auto-complete, and I have the delusion that integrating one of the two into the tarball would help solve this problem). We could do it by moving company-mode to emacs.git, but IIRC the maintainer of company-mode would prefer to keep it in elpa.git, so the other option is to bundle that ELPA package into the tarball. I never thought of this as a way to move stuff out of emacs.git. Yet, there is one case where I think it would be beneficial to move a package out of emacs.git only to re-integrate it back into the tarball: Org mode. Org mode is really managed as a separate package (which sadly isn't even present in elpa.git) that happens to be bundled in the tarball: almost no code in the rest of Emacs cares about Org, and the Org code is not tightly dependent on the specific Emacs version with which it is shipped. So IMO it would make more sense to keep Org outside of emacs.git (and save us the trouble of syncing), tho we'd still want to distribute it in Emacs's tarball, since it's an extremely popular package. Stefan