From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: feature/integrated-elpa 4f6df43 15/23: README added Date: Tue, 18 Oct 2016 20:46:05 +0300 Message-ID: <837f95wnxe.fsf@gnu.org> References: <20160916203414.25203.87032@vcs.savannah.gnu.org> <8660p3qd99.fsf@realize.ch> <831szrhwsr.fsf@gnu.org> <8760p12qzw.fsf@russet.org.uk> <83vax0en1u.fsf@gnu.org> <87pon5ek3q.fsf@russet.org.uk> <87twcgttjf.fsf@russet.org.uk> <86a8e7symk.fsf@realize.ch> <8737jzl4u9.fsf@russet.org.uk> <8337jz8dg8.fsf@gnu.org> <83insv3tnl.fsf@gnu.org> <83d1j33qgg.fsf@gnu.org> <87wph96cto.fsf@russet.org.uk> <83h98axk5z.fsf@gnu.org> <8760opkdz3.fsf@russet.org.uk> <83inspwvvy.fsf@gnu.org> <87shrtfv9r.fsf@russet.org.uk> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1476812817 13575 195.159.176.226 (18 Oct 2016 17:46:57 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 18 Oct 2016 17:46:57 +0000 (UTC) Cc: jwiegley@gmail.com, andrewjmoreton@gmail.com, emacs-devel@gnu.org To: phillip.lord@russet.org.uk (Phillip Lord) Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Oct 18 19:46:52 2016 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 1bwYTA-0000Xa-69 for ged-emacs-devel@m.gmane.org; Tue, 18 Oct 2016 19:46:32 +0200 Original-Received: from localhost ([::1]:43107 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bwYTC-0002TR-79 for ged-emacs-devel@m.gmane.org; Tue, 18 Oct 2016 13:46:34 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:44030) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bwYT6-0002S7-Fo for emacs-devel@gnu.org; Tue, 18 Oct 2016 13:46:29 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bwYT3-000859-5t for emacs-devel@gnu.org; Tue, 18 Oct 2016 13:46:28 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:38731) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bwYT3-000853-25; Tue, 18 Oct 2016 13:46:25 -0400 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:1451 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1bwYT0-00046N-JV; Tue, 18 Oct 2016 13:46:23 -0400 In-reply-to: <87shrtfv9r.fsf@russet.org.uk> (phillip.lord@russet.org.uk) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e 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:208435 Archived-At: > From: phillip.lord@russet.org.uk (Phillip Lord) > Cc: jwiegley@gmail.com, andrewjmoreton@gmail.com, emacs-devel@gnu.org > Date: Tue, 18 Oct 2016 17:59:28 +0100 > > >> - Enable a built emacs to build and test all packages in ELPA whether > >> they are core/tarball or not. > > > > Can this be done while keeping the current structure under lisp/ > > intact and putting packages from ELPA under lisp/ ? If yes, I think > > this is what we all want. > > > I can easily do: > > > EMACS/lisp > EMACS/lisp/lots-of-files.el > EMACS/lisp/textmodes/ > EMACS/lisp/progmodes > EMACS/lisp/packages > EMACS/lisp/packages/package-1 > EMACS/lisp/packages/package-2 > EMACS/lisp/packages/package-3 As already discussed, this is not what we want. > I could less easily do: > > EMACS/lisp > EMACS/lisp/lots-of-files.el > EMACS/lisp/textmodes/package-1 > EMACS/lisp/progmodes/package-2 > EMACS/lisp/emacs-lisp/package-3 This is what we want. IOW, we want foo.el to live in the same directory it is now, even if its Git repository will be on ELPA. > This requires updating the current build process to exclude multiple > directories Why do we need to exclude directories during the build? And what does "exclude" mean in this context? > I also dislike this, because I think it mixes up files of different > kinds in the tree (that is files which are in place in the Emacs git > repo, and those which are not). There are no different kinds. They are all of the same kind: Lisp packages that are bundled with a release tarball. The fact that some of them are in a separate Git repo doesn't make them a different kind. We want the move to ELPA to be transparent as far as the Emacs lisp/ directory structure is concerned. > Finally, it would no doubt be possible to do: > > EMACS/lisp > EMACS/lisp/textmodes/package-1a.el > EMACS/lisp/textmodes/package-1b.el > EMACS/lisp/textmodes/package-1c.el > EMACS/lisp/progmodes/package-2.el > EMACS/lisp/emacs-lisp/package-3.el Where 1a, 1b, and 1c are different versions of the same package? This is not required; the updates of bundled packages should go into ~/.emacs.d/elpa/, I think.