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: [Emacs-diffs] feature/integrated-elpa 4f6df43 15/23: README added Date: Sat, 08 Oct 2016 13:01:38 +0300 Message-ID: <8360p3i2gt.fsf@gnu.org> References: <20160916203414.25203.87032@vcs.savannah.gnu.org> <874m582ixv.fsf@russet.org.uk> <871t0apsxm.fsf@russet.org.uk> <87shsm7hi6.fsf@russet.org.uk> <83a8eucwi2.fsf@gnu.org> <878tudgwlq.fsf@russet.org.uk> <8360pgoyo4.fsf@gnu.org> <87d1jn3ws9.fsf@russet.org.uk> <83a8eqoi08.fsf@gnu.org> <87d1jlacsh.fsf@russet.org.uk> <867f9t4n4t.fsf@realize.ch> <874m4x8sq5.fsf@russet.org.uk> <8637kh4j1u.fsf@realize.ch> <87wpht4b1i.fsf@russet.org.uk> <86y4292m2u.fsf@realize.ch> <8737kd8vfh.fsf@russet.org.uk> <867f9n2r6s.fsf@realize.ch> <87a8egw2az.fsf@russet.org.uk> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1475920962 23790 195.159.176.226 (8 Oct 2016 10:02:42 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 8 Oct 2016 10:02:42 +0000 (UTC) Cc: a.s@realize.ch, monnier@iro.umontreal.ca, 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 Sat Oct 08 12:02:38 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 1bsoSf-00057T-6C for ged-emacs-devel@m.gmane.org; Sat, 08 Oct 2016 12:02:33 +0200 Original-Received: from localhost ([::1]:40269 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bsoSd-0001KL-Ro for ged-emacs-devel@m.gmane.org; Sat, 08 Oct 2016 06:02:31 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:54471) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bsoRj-0001IR-NP for emacs-devel@gnu.org; Sat, 08 Oct 2016 06:01:36 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bsoRg-0000C5-Ci for emacs-devel@gnu.org; Sat, 08 Oct 2016 06:01:35 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:44769) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bsoRg-0000BZ-9n; Sat, 08 Oct 2016 06:01:32 -0400 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:2523 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1bsoRe-0006aE-AA; Sat, 08 Oct 2016 06:01:30 -0400 In-reply-to: <87a8egw2az.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:208080 Archived-At: > From: phillip.lord@russet.org.uk (Phillip Lord) > Cc: Eli Zaretskii , , > Date: Fri, 07 Oct 2016 17:29:08 +0100 > > Alain Schneble writes: > >> Not if we are using package.el to make the packages available. It is > >> package.el which sets the load path, loads the autoloads file, that sort > >> of thing. > > > > After all, what would we gain from using package.el to do this > > bootstrapping for the ELPA core packages? > > Packages in already in package.el format can be directly used within > Emacs. What do you mean by "directly used"? Directly as opposed to what? > This requires no changes in the file layout, and means that > packages will only be built with a single system (i.e. both Emacs core > and ELPA will be build with package.el). Why would the Emacs build require package.el to do anything at all? And what kind of build do you have in mind here? We have: . build out of Git repo . build of the release tarball as distributed from ftp.gnu.org . build of the release tarball after updating some packages from ELPA > As a secondary benefit, this means I can build and test an ELPA checkout > directly as part of the Emacs build, which should be useful for finding > regressions. ELPA packages should be logically part of Emacs, just in a different Git repo. So this goal should be supported, of course. But I don't understand why it would require using a separate directory tree for ELPA packages. > It also, of course, means that files from ELPA would now be duplicated > in core Emacs because they would have been copied. ??? Copied from where to where? And why? I don't understand why they would need to be copied anywhere, they just need to be downloaded directly to where they belong in the Emacs directory structure. > So, when developing Emacs, there would be version controlled .el > source files and non-version controlled copied .el files in the same > location. We already have that; see charscript.el. Why having some moe unversioned *.el files would hurt or be any different? > You would have to remember to edit the former, but not the latter. ??? Unversioned files can be edited to your heart's content, they will just be overwritten on the next update. We successfully deal with this with the generated files, I see no reasons why we couldn't do the same with ELPA packages.