From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Andy Moreton Newsgroups: gmane.emacs.devel Subject: Re: feature/integrated-elpa 4f6df43 15/23: README added Date: Fri, 14 Oct 2016 14:51:15 +0100 Message-ID: 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> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1476453217 19832 195.159.176.226 (14 Oct 2016 13:53:37 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 14 Oct 2016 13:53:37 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (windows-nt) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Oct 14 15:53:29 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 1bv2v5-00025L-2U for ged-emacs-devel@m.gmane.org; Fri, 14 Oct 2016 15:53:07 +0200 Original-Received: from localhost ([::1]:47461 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bv2v3-0004hx-Ku for ged-emacs-devel@m.gmane.org; Fri, 14 Oct 2016 09:53:05 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:59990) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bv2u1-0004cM-FC for emacs-devel@gnu.org; Fri, 14 Oct 2016 09:52:05 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bv2tu-0003ff-Vr for emacs-devel@gnu.org; Fri, 14 Oct 2016 09:52:00 -0400 Original-Received: from [195.159.176.226] (port=41407 helo=blaine.gmane.org) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bv2tu-0003du-Pu for emacs-devel@gnu.org; Fri, 14 Oct 2016 09:51:54 -0400 Original-Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1bv2tT-0007u3-RO for emacs-devel@gnu.org; Fri, 14 Oct 2016 15:51:27 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 39 Original-X-Complaints-To: usenet@blaine.gmane.org Cancel-Lock: sha1:MMPO4XikWD/zokKEs2zt/y9g5lg= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 195.159.176.226 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:208244 Archived-At: On Fri 14 Oct 2016, Eli Zaretskii wrote: >> From: phillip.lord@russet.org.uk (Phillip Lord) >> Cc: Eli Zaretskii , , >> Date: Fri, 14 Oct 2016 09:20:14 +0100 >> >> > Do you really want to give up this standard file structure? >> >> >> Yes, because it is not standard. It's one of two standards. >> >> If you install org with package.el, then you get >> >> ~/.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. Keeping each package in ELPA format ensures that replacing the package can be done easily, as everything is isolated in a single directory. 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. 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. There are many more users of emacs than developers, so the design should be aimed at utility and convenience for users. AndyM