From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Emacs release and bundling GNU Elpa Date: Sun, 21 Jun 2015 20:45:36 -0400 Message-ID: References: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1434933970 1474 80.91.229.3 (22 Jun 2015 00:46:10 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 22 Jun 2015 00:46:10 +0000 (UTC) Cc: emacs-devel To: Artur Malabarba Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jun 22 02:46:01 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 1Z6ps9-000723-I5 for ged-emacs-devel@m.gmane.org; Mon, 22 Jun 2015 02:46:01 +0200 Original-Received: from localhost ([::1]:37679 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z6ps9-0006C6-1S for ged-emacs-devel@m.gmane.org; Sun, 21 Jun 2015 20:46:01 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:59250) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z6prt-0006By-3M for emacs-devel@gnu.org; Sun, 21 Jun 2015 20:45:46 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Z6prp-0006Dx-TM for emacs-devel@gnu.org; Sun, 21 Jun 2015 20:45:45 -0400 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.181]:59068) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z6prp-00069p-DV for emacs-devel@gnu.org; Sun, 21 Jun 2015 20:45:41 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A0AsEwA731xV/zDyd0tcgxCEAoVVuzcJh0sEAgKBPDkUAQEBAQEBAYEKQQWDXQEBAwFWIwULCw4mEhQYDSSINwjPIwEBAQcCAR+LOoUFB4QtBbM/gUUjYYMzIoJ4AQEB X-IPAS-Result: A0AsEwA731xV/zDyd0tcgxCEAoVVuzcJh0sEAgKBPDkUAQEBAQEBAYEKQQWDXQEBAwFWIwULCw4mEhQYDSSINwjPIwEBAQcCAR+LOoUFB4QtBbM/gUUjYYMzIoJ4AQEB X-IronPort-AV: E=Sophos;i="5.13,465,1427774400"; d="scan'208";a="127901872" Original-Received: from 75-119-242-48.dsl.teksavvy.com (HELO ceviche.home) ([75.119.242.48]) by ironport2-out.teksavvy.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 21 Jun 2015 20:45:38 -0400 Original-Received: by ceviche.home (Postfix, from userid 20848) id 1C606660F3; Sun, 21 Jun 2015 20:45:36 -0400 (EDT) In-Reply-To: (Artur Malabarba's message of "Sun, 21 Jun 2015 10:59:06 +0100") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 206.248.154.181 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:187360 Archived-At: > Stefan, you've mentioned a few times here you'd like some > build-scripts integration between GNU Elpa and the Emacs source at > build time. Could you clarify on what it would take to get that done? Good question. It's mostly open. I see it happening in steps, mostly for historical reasons: step-1: we change the tarball-building script so as to pull some packages from elpa.git and include them somewhere under the `lisp' directory (for example) in the tarballs we distribute. step-2: we change the build scripts used from a Git checkout so they can also use those packages from elpa.git. step-3: we change the build scripts again so they always use those packages from elpa.git. At step 3, we'd have the following novelties: - the end user has to checkout both emacs.git and elpa.git before she can build Emacs (I suspect there will be some resistance, here). - packages in emacs/lisp can start to depend on packages from elpa.git. - we could even include preload some elpa.git packages (i.e. from loadup.el). I'm not exactly sure we'll ever get to step 3. > - Is it just a matter of pulling in some extra specified packages when > building the tarball? At first, yes. Tho the "just" has to be adjusted based on the need to specify exactly which version of the package to include. > - What/where are the files involved in that process? admin/make-tarball.txt should give you all the answers. But the main step is clearly to run the `make-dist' script. Stefan