From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eli Zaretskii Subject: Re: Sync up the org in emacs master to org maint branch? Date: Thu, 02 Feb 2017 22:37:36 +0200 Message-ID: <83o9ykuy5r.fsf@gnu.org> References: <87k29d7zvw.fsf@engster.org> <87fuk08i01.fsf@engster.org> <87d1f36xnc.fsf@engster.org> <83tw8cv6pj.fsf@gnu.org> <8760kseb7e.fsf@engster.org> Reply-To: Eli Zaretskii Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:41946) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cZO8y-0002PT-PK for emacs-orgmode@gnu.org; Thu, 02 Feb 2017 15:38:16 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cZO8v-0006ac-6C for emacs-orgmode@gnu.org; Thu, 02 Feb 2017 15:38:12 -0500 In-reply-to: <8760kseb7e.fsf@engster.org> (message from David Engster on Thu, 02 Feb 2017 18:47:49 +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: David Engster Cc: emacs-devel@gnu.org, bzg@gnu.org, emacs-orgmode@gnu.org, kaushal.modi@gmail.com, larsi@gnus.org, phillip.lord@russet.org.uk > From: David Engster > Cc: Lars Ingebrigtsen , bzg@gnu.org, emacs-devel@gnu.org, phillip.lord@russet.org.uk, emacs-orgmode@gnu.org, kaushal.modi@gmail.com > Date: Thu, 02 Feb 2017 18:47:49 +0100 > > > I believe the intent is to make it so that checking out and building > > Emacs also checks out and builds all the packages that are intended to > > be part of a release tarball. If we indeed do that this way, there > > will be no difference, QA-wise, between core packages and ELPA > > packages that are logically part of an Emacs release. > > That's not how I understood it. I hope you have misunderstood, and not me. > It was always said that Emacs must not depend on those ELPA packages > that are shipped with the release I'm talking about building Emacs from Git, not from a release tarball. For the latter, you are right, and we are in agreement. But that's not relevant for the issue at hand, which appears to be the attention which such ELPA packages will get from Emacs developers. For that, building a fresh checkout should also build the latest versions from ELPA, from a branch that the package maintainers will designate as the equivalent of the Emacs master branch. > which implies that they are not supposed to be present at a "normal" > checkout. I don't see how it implies that. Release tarballs are prepared specially for a release, so their build procedures don't have to be identical to building from Git. > Otherwise, what difference would it make? Ask the package maintainers, they see significant advantages in being able to release interim versions independent of Emacs releases. But we are not talking about that aspect, we are talking about the parallel development of core and the packages.