From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: David Engster Newsgroups: gmane.emacs.devel,gmane.emacs.orgmode Subject: Re: Sync up the org in emacs master to org maint branch? Date: Thu, 02 Feb 2017 18:47:49 +0100 Message-ID: <8760kseb7e.fsf@engster.org> References: <87k29d7zvw.fsf@engster.org> <87fuk08i01.fsf@engster.org> <87d1f36xnc.fsf@engster.org> <83tw8cv6pj.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1486057697 10353 195.159.176.226 (2 Feb 2017 17:48:17 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Thu, 2 Feb 2017 17:48:17 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux) Cc: emacs-devel@gnu.org, bzg@gnu.org, emacs-orgmode@gnu.org, kaushal.modi@gmail.com, Lars Ingebrigtsen , phillip.lord@russet.org.uk To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Feb 02 18:48:09 2017 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cZLUM-0002I6-Hm for ged-emacs-devel@m.gmane.org; Thu, 02 Feb 2017 18:48:06 +0100 Original-Received: from localhost ([::1]:58205 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cZLUP-0008MP-QV for ged-emacs-devel@m.gmane.org; Thu, 02 Feb 2017 12:48:09 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:54787) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cZLUH-0008K7-0Y for emacs-devel@gnu.org; Thu, 02 Feb 2017 12:48:02 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cZLUG-0008K6-7M for emacs-devel@gnu.org; Thu, 02 Feb 2017 12:48:01 -0500 Original-Received: from randomsample.de ([5.45.97.173]:33436) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cZLU9-0008Gz-JM; Thu, 02 Feb 2017 12:47:53 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=randomsample.de; s=a; h=Content-Type:MIME-Version:Message-ID:Date:References:In-Reply-To:Subject:Cc:To:From; bh=uYJYnPpv9BZ7OzPn8YbiB+qukqxaxIFWKM6ELxmbGos=; b=NAypTYpXuxtFwH0c5rQpsGI+fs9uieaAwCw2Au2qORRrJGz5XZftJ6VBmrMSz0qAexlnUIc7k+HEryBNXgNgzklFq2Xp2jOXvvRdGHh1WhUO0ZfRkVYb3OGisDiXb0bT; Original-Received: from ip4d16b353.dynamic.kabel-deutschland.de ([77.22.179.83] helo=isaac) by randomsample.de with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1cZLU6-0002P9-D2; Thu, 02 Feb 2017 18:47:50 +0100 In-Reply-To: <83tw8cv6pj.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 02 Feb 2017 19:32:56 +0200") X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy] X-Received-From: 5.45.97.173 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 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" Xref: news.gmane.org gmane.emacs.devel:211884 gmane.emacs.orgmode:111863 Archived-At: Eli Zaretskii writes: >> From: Lars Ingebrigtsen >> Date: Thu, 02 Feb 2017 13:10:07 +0100 >> Cc: Bastien Guerry , Emacs developers , > >> Phillip Lord , >> emacs-org list , >> Kaushal Modi >> >> If Django had traditionally always been distributed along with Python, >> and maintained in the Python repo, and the suggestion now would be to >> move Django to a part of the Python repo that very few developers look >> at, but Django would continue to be distributed with Python, and all >> Django bug reports would continue to go to the Python bug repository, >> and Python developers would continue to be responsible for QA and bug >> fixing of Django. > > 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. It was always said that Emacs must not depend on those ELPA packages that are shipped with the release, which implies that they are not supposed to be present at a "normal" checkout. Otherwise, what difference would it make? (Besides requiring more cumbersome tooling to make this all work.) -David