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: Wed, 28 Sep 2016 18:02:19 +0300 Message-ID: <8360pgoyo4.fsf@gnu.org> References: <20160916203414.25203.87032@vcs.savannah.gnu.org> <20160916203416.8DF2F220166@vcs.savannah.gnu.org> <87vaxsjmvu.fsf@russet.org.uk> <878tunj2wr.fsf@russet.org.uk> <874m582ixv.fsf@russet.org.uk> <871t0apsxm.fsf@russet.org.uk> <87shsm7hi6.fsf@russet.org.uk> <83a8eucwi2.fsf@gnu.org> <878tudgwlq.fsf@russet.org.uk> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1475074991 21735 195.159.176.226 (28 Sep 2016 15:03:11 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 28 Sep 2016 15:03:11 +0000 (UTC) Cc: 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 Wed Sep 28 17:03:01 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 1bpGNh-0002o6-AO for ged-emacs-devel@m.gmane.org; Wed, 28 Sep 2016 17:02:45 +0200 Original-Received: from localhost ([::1]:59410 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bpGNe-0001oh-Rw for ged-emacs-devel@m.gmane.org; Wed, 28 Sep 2016 11:02:42 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:43950) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bpGNP-0001jJ-KC for emacs-devel@gnu.org; Wed, 28 Sep 2016 11:02:31 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bpGNK-0007qE-UX for emacs-devel@gnu.org; Wed, 28 Sep 2016 11:02:26 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:58067) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bpGNK-0007pu-Rf; Wed, 28 Sep 2016 11:02:22 -0400 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:1195 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1bpGNI-0006BX-NV; Wed, 28 Sep 2016 11:02:21 -0400 In-reply-to: <878tudgwlq.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:207861 Archived-At: > From: phillip.lord@russet.org.uk (Phillip Lord) > Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org > Date: Tue, 27 Sep 2016 17:01:53 +0100 > > > Why does it have to be a separate directory? Why cannot those > > packages be downloaded into their current places, where they belong in > > one of the subdirectories of lisp/? > > > The build process is different. I use package.el to compile, and to > build the autoloads and the -pkg.el file. This could be done in the lisp > directory, but I'd have to exclude this directory from the normal build > process in the lisp directory. Can't we handle the differences during the build without separating directories? E.g., we already have some files that should not be byte-compiled, and we handle it with a file-local variable. Can't we do something similar with this issue? > I'm not at all wedded to the directory structure. This is just a > proof-of-principle. It can be what ever we want. Is there a problem with > introducing a new top level? It's not a catastrophe, but it runs the risk of raising the annoyance level when looking for a certain file. Already there are some Lisp files for which I never know in what subdirectory they should live. Having yet another subtree will make things worse, since there's no way of knowing up front whether a file is in core or not.