From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: policy discussion on bundling ELPA packages in the emacs tarball Date: Mon, 25 Jan 2021 21:53:00 +0200 Message-ID: <83y2gg23qb.fsf@gnu.org> References: <86eeifawx8.fsf@stephe-leake.org> <87czxygdl9.fsf@russet.org.uk> <86tur88izp.fsf@stephe-leake.org> <86h7n880lo.fsf@stephe-leake.org> <83y2gk3rin.fsf@gnu.org> <86o8he6y4k.fsf@stephe-leake.org> <8335yq4350.fsf@gnu.org> <86k0s26qqt.fsf@stephe-leake.org> <83sg6q2is5.fsf@gnu.org> <86wnw06cgo.fsf@stephe-leake.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="8780"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org, phillip.lord@russet.org.uk To: Stephen Leake Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Jan 25 20:54:27 2021 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1l47wQ-0002AB-SI for ged-emacs-devel@m.gmane-mx.org; Mon, 25 Jan 2021 20:54:26 +0100 Original-Received: from localhost ([::1]:49332 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1l47wP-0004de-Ra for ged-emacs-devel@m.gmane-mx.org; Mon, 25 Jan 2021 14:54:25 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:48834) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1l47ux-0003RU-1m for emacs-devel@gnu.org; Mon, 25 Jan 2021 14:52:55 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:59416) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1l47uw-0005Xo-0z; Mon, 25 Jan 2021 14:52:54 -0500 Original-Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:4093 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1l47uu-0006bq-Ny; Mon, 25 Jan 2021 14:52:53 -0500 In-Reply-To: <86wnw06cgo.fsf@stephe-leake.org> (message from Stephen Leake on Mon, 25 Jan 2021 11:30:47 -0800) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:263414 Archived-At: > From: Stephen Leake > Cc: phillip.lord@russet.org.uk, emacs-devel@gnu.org > Date: Mon, 25 Jan 2021 11:30:47 -0800 > > Doing 'git clone @git.savannah.gnu.org:/srv/git/emacs.git' > results in disk space usage of around 300 MB in emacs/.git, and does not > populate emacs/elpa. Where did emacs/elpa come from? I don't think we ever discussed such a beast, and I don't understand what it is and what it will contain. > Doing 'git clone @git.savannah.gnu.org:/srv/git/emacs.git > --recurse-submodules' results in disk space usage of around 500 MB in > emacs/.git, and populates emacs/elpa. > > If we implemented the suggestion to split the ELPA repository into one > repository per bundled package, that extra 200 MB would be smaller. > > Is 200 MB acceptable? That's a the question I can answer, because I have no clear idea what is included in those 200MB, and in particular how much of that is ballast we don't need for the purposes of maintaining Emacs and building its development versions. Maybe if you explained why splitting ELPA into several repositories would save some of that disk space, I could then try answering the question. > I can see some reasons for the current git design; _all_ of the info needed > to update the code for project foo is in foo/.git. Worktrees stretch > that; allowing submodules to be worktree-like references to yet another > repository somewhere else would probably break many things in git. I think we should first find a way to have a single worktree with all the bundled packages that come from ELPA. How to have several worktrees from that is something we should consider later.