From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Artur Malabarba Newsgroups: gmane.emacs.devel Subject: Re: Emacs release and bundling GNU Elpa Date: Tue, 23 Jun 2015 11:55:01 +0100 Message-ID: References: <83si9jhi5u.fsf@gnu.org> <83k2uvh92y.fsf@gnu.org> Reply-To: bruce.connor.am@gmail.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1435056916 29064 80.91.229.3 (23 Jun 2015 10:55:16 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 23 Jun 2015 10:55:16 +0000 (UTC) Cc: Stefan Monnier , emacs-devel To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jun 23 12:55:15 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 1Z7LrF-0002Uy-L6 for ged-emacs-devel@m.gmane.org; Tue, 23 Jun 2015 12:55:13 +0200 Original-Received: from localhost ([::1]:44521 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z7LrF-0004gw-1B for ged-emacs-devel@m.gmane.org; Tue, 23 Jun 2015 06:55:13 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:58514) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z7Lr7-0004eb-T6 for emacs-devel@gnu.org; Tue, 23 Jun 2015 06:55:10 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Z7Lr6-0000bQ-1N for emacs-devel@gnu.org; Tue, 23 Jun 2015 06:55:05 -0400 Original-Received: from mail-lb0-x22c.google.com ([2a00:1450:4010:c04::22c]:35410) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z7Lr4-0000X4-4b; Tue, 23 Jun 2015 06:55:02 -0400 Original-Received: by lbbwc1 with SMTP id wc1so4066598lbb.2; Tue, 23 Jun 2015 03:55:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:content-transfer-encoding; bh=43KFF4yE4VJpMBY6wdmDz/P3A+eM0DSl3vfQY8Jot+w=; b=zPm18i7r37XbiA+As+lh9UF+Zn5aWIfOOaaVAohS8WfNY8Xbv6jKGcC89z9hyLbrXn I15XcGPmgESb4CpwUdGFBUDYD8y0fJYBz884JVkO07WruwKagKjvMpGwZs8yO7Dk7WQ+ bKJtyvijY3sN3DtINfVXegrjZHIFCQOxgu1zYEgzP63VSLf9Oag8s7HOlO+PmNjghro2 0U+Hg7vRY4Z8jUSQBePstOiVVrLRtl6xLyZJv72/rFi5uMRrHOgC2hjSiZ3ZW3/4SEZ0 Ux6QBos0Y3HoI6ElGyxdNmYRiXzwFgQZKm9kt5no36lWv3dG+4gfuq7QtW4WHK1mMSP0 ECyg== X-Received: by 10.112.139.130 with SMTP id qy2mr34501139lbb.21.1435056901177; Tue, 23 Jun 2015 03:55:01 -0700 (PDT) Original-Received: by 10.25.214.133 with HTTP; Tue, 23 Jun 2015 03:55:01 -0700 (PDT) In-Reply-To: <83k2uvh92y.fsf@gnu.org> X-Google-Sender-Auth: iw9FLnNYsFz_ANyMVOnyRMlck_k X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:4010:c04::22c 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:187404 Archived-At: >> > and less exposure of packages to people who track development on >> > master, >> >> These packages will effectively be part of master. > > Only if one decides to pull them. Since that's at least a bit of an > additional hassle, one could decide not to bother. If this is taken forward, copying these packages sources from elpa.git to emacs not be optional, i.e., it will be a mandatory step in the make command. This is the only way for other packages in =E2=80=9C./lisp/= =E2=80=9D to be able to depend on these imported packages. Updating the submodule will only be necessary once in a while (when the configuration file specifies a newer version for a package than the version you have locally, and the makefile will tell you about that), but it will be necessary. >> > . We'd need to find a way of providing ChangeLogs for the packages, >> > either by merging their Git logs somehow, or by keeping their >> > ChangeLogs in separate directories (which would mean each package >> > will have its own directory, making load-path longer). >> >> Keep their ChangeLogs in the same place as their source (in the >> "./elpa.git/packages/package-name/" directory). This has nothing to do >> with the load-path. The load-path will point to "./lisp/from-elpa" >> (which is where we copy the sources before compiling). > > Aren't you forgetting that ChangeLog files need to be part of the > release tarball? Or do you mean we will have each package twice in a > tarball, in 2 different directories? Good point. How about, whenever we copy the source to =E2=80=9C./lisp/from-elpa/=E2=80=9D we also copy the ChangeLog to the same = place, but rename it to something like ChangeLog-packagename? So they can all coexist in that directory.