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: Fri, 14 Oct 2016 17:13:50 +0300 Message-ID: <83insv3tnl.fsf@gnu.org> References: <20160916203414.25203.87032@vcs.savannah.gnu.org> <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> <8360p3i2gt.fsf@gnu.org> <86a8efqf9p.fsf@realize.ch> <8337k7hysd.fsf@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> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1476454591 6009 195.159.176.226 (14 Oct 2016 14:16:31 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 14 Oct 2016 14:16:31 +0000 (UTC) Cc: emacs-devel@gnu.org To: Andy Moreton Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Oct 14 16:16:27 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 1bv3HK-0007LE-OO for ged-emacs-devel@m.gmane.org; Fri, 14 Oct 2016 16:16:06 +0200 Original-Received: from localhost ([::1]:47559 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bv3HJ-00063U-5a for ged-emacs-devel@m.gmane.org; Fri, 14 Oct 2016 10:16:05 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:37184) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bv3FR-0005Jc-66 for emacs-devel@gnu.org; Fri, 14 Oct 2016 10:14:10 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bv3FM-0001it-2H for emacs-devel@gnu.org; Fri, 14 Oct 2016 10:14:07 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:54196) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bv3FL-0001io-V9; Fri, 14 Oct 2016 10:14:03 -0400 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:2199 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpa (Exim 4.82) (envelope-from ) id 1bv3FJ-00030S-70; Fri, 14 Oct 2016 10:14:03 -0400 In-reply-to: (message from Andy Moreton on Fri, 14 Oct 2016 14:51:15 +0100) 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:208245 Archived-At: > From: Andy Moreton > Date: Fri, 14 Oct 2016 14:51:15 +0100 > > >> ~/.emacs.d/elpa/org/org > >> ~/.emacs.d/elpa/org/etc/ORG-NEWS > >> ~/.emacs.d/elpa/org/org.el > >> > >> So, org-mode has to support two independent directory layouts. > > > > But Org already supports those two formats. We don't require Org to > > do anything that it doesn't already do. So staying with the current > > structure of lisp/ in the Emacs tree doesn't add any new requirements. > > But that would do nothing to reduce the unnecessary and duplicated > packaging work. I'm not sure I understand what duplicated work you have in mind. Org developers will still put Org on ELPA in the same directory structure they do now. When Org is imported into Emacs, as part of building a release tarball or as part of building from the repository, each file will be put in its natural place in the Emacs source tree, either by package.el or by some other means, and will replace any previous Org files, if there were such. When end-users want to upgrade to a version of Org newer than what they have bundled in the latest Emacs release, the Org files will be placed under ~/.emacs.d/elpa/org/, as they are now. > Keeping each package in ELPA format ensures that replacing the package > can be done easily, as everything is isolated in a single directory. I see no particular difficulties in putting several files into several directories, software can and does do that all the time. It's not like we will be asking users to do this manually. > If the package is shipped in the emacs tarball and the user then > upgrades to a newer version from ELPA, only the load path needs to > change. This part doesn't need to change at all, under my proposal. > In additon, the user can easily compare the changes bewteen the package > version shipped in the emacs tarball and the updated one fetched from > ELPA, as the package layout is the same. What for? There should be NEWS in the new Org release. Those more details regarding the changes can always look in the Org Git repo. > There are many more users of emacs than developers, so the design > should be aimed at utility and convenience for users. That's the main motivation for my proposal, indeed.