From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Phillip Lord Newsgroups: gmane.emacs.devel Subject: Re: policy discussion on bundling ELPA packages in the emacs tarball Date: Fri, 29 Jan 2021 17:47:39 +0000 Message-ID: <87y2gbskhw.fsf@russet.org.uk> 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> <83y2gg23qb.fsf@gnu.org> <867dny5u4u.fsf@stephe-leake.org> <83sg6mz704.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="11774"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: Stephen Leake , emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Jan 29 18:54:11 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 1l5XyF-0002uS-74 for ged-emacs-devel@m.gmane-mx.org; Fri, 29 Jan 2021 18:54:11 +0100 Original-Received: from localhost ([::1]:46826 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1l5XyE-0006wz-6u for ged-emacs-devel@m.gmane-mx.org; Fri, 29 Jan 2021 12:54:10 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:53304) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1l5Xs1-0008Nw-5S for emacs-devel@gnu.org; Fri, 29 Jan 2021 12:47:45 -0500 Original-Received: from cloud103.planethippo.com ([78.129.138.110]:37032) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1l5Xrz-0004np-6J; Fri, 29 Jan 2021 12:47:44 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=russet.org.uk; s=default; h=Content-Type:MIME-Version:Message-ID: In-Reply-To:Date:References:Subject:Cc:To:From:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=91tjXn5lTOERZ0CPg8rvABAcL8rGoJdQfPjaesgQEeY=; b=hDUCjsi8pE/2xAz95lkFNFDgc GWndfAzMnZOByJkKq/2jN8BrkZSImO0vpaO7TwWoo1BFXHLrH2LRhgTdGt8YO1JsvmxeBEgdlbiYr 1uRWgUhFUi4N1nTeG+9cmu27dN3zJlVECbQZcitZ0hM3lZDuJGzuegQEsmB2iq1f+jhN1sStTUT4W y+uTWilvEY6moasuQqm4+jRhm3DN6mSkAqr+f/dtQ3iVo+rRQA546hYG/C7GfPJepgCBMn4Rma79p fUUbr7cPpi2PWMxgCXH7u7cGafQ4nSPsq6t37mboBREI41fIM6Vcc2nRBcELz5Jy8OXoRdT1ggh6c AeNqfVeaQ==; Original-Received: from cpc142648-benw12-2-0-cust627.16-2.cable.virginm.net ([82.10.74.116]:54694 helo=russet.org.uk) by cloud103.planethippo.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.93) (envelope-from ) id 1l5Xrw-0008M1-Nn; Fri, 29 Jan 2021 17:47:40 +0000 In-Reply-To: <83sg6mz704.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 27 Jan 2021 18:20:27 +0200") X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - cloud103.planethippo.com X-AntiAbuse: Original Domain - gnu.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - russet.org.uk X-Get-Message-Sender-Via: cloud103.planethippo.com: authenticated_id: phillip.lord@russet.org.uk X-Authenticated-Sender: cloud103.planethippo.com: phillip.lord@russet.org.uk Received-SPF: none client-ip=78.129.138.110; envelope-from=phillip.lord@russet.org.uk; helo=cloud103.planethippo.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001 autolearn=ham autolearn_force=no X-Spam_action: no action 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:263581 Archived-At: Eli Zaretskii writes: >> >> 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. >> >> I don't think we can leave it until later; if we choose a design that >> explicitly prohibits worktrees, there is nothing that can be done later. > > It will mean that people who use worktrees will have to find some way > of doing that, or give up worktrees. But IMO the convenience of > bundling a package and handling such a bundled package trumps the > convenience of people who use worktrees a lot. To give you an idea of why I use worktrees, it is because Emacs does not really do an out of source build. So, on the windows build machine I currently have: emacs-build/master emacs-build/emacs-27 emacs-build/emacs-27.1.91 emacs-build/feature/native-comp For emacs-27 I only ever do full builds; creating a new worktree means that I start from clean, but is clearly not the only way to achieve this. For emacs-28, though, when I release snapshots, I do not (always) do clean builds. I use the .elc files from the previous build. The same will be true for native-comp once I have that working enough to build snapshots. It's not a disaster, but I will have to switch the windows packaging scripts away from this schema if worktrees do not work; I guess I will use mulitple clones instead. This may mean I run out of disk space on my windows build machine, though which only has a tiny disc, I don't know. It depends on how well git works, and how clever Windows file system compression is. I do the same on my working machines, so I can keep multiple branches open. So I can test master, but jump back to a release branch if it breaks and I am busy. I guess I will use multiple clones here again. Phil