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: decision on moving core packages to ELPA; also move to obsolete? Date: Wed, 16 Dec 2020 19:56:52 +0200 Message-ID: <83o8it8wij.fsf@gnu.org> References: <86a6ugnopl.fsf@stephe-leake.org> <83im94b17m.fsf@gnu.org> <834kknatxs.fsf@gnu.org> <83sg86apqb.fsf@gnu.org> <865z52oqfp.fsf@stephe-leake.org> <83ft46akpm.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="21311"; mail-complaints-to="usenet@ciao.gmane.io" Cc: daniele@grinta.net, stephen_leake@stephe-leake.org, emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Dec 16 18:58:03 2020 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 1kpb3q-0005Qg-VF for ged-emacs-devel@m.gmane-mx.org; Wed, 16 Dec 2020 18:58:02 +0100 Original-Received: from localhost ([::1]:59994 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kpb3p-0001M3-UG for ged-emacs-devel@m.gmane-mx.org; Wed, 16 Dec 2020 12:58:01 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:56426) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kpb2o-0000r4-0Y for emacs-devel@gnu.org; Wed, 16 Dec 2020 12:56:58 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:59734) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kpb2n-0005hX-Nw; Wed, 16 Dec 2020 12:56:57 -0500 Original-Received: from [176.228.60.248] (port=3931 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1kpb2n-0003vg-3O; Wed, 16 Dec 2020 12:56:57 -0500 In-Reply-To: (message from Stefan Monnier on Tue, 15 Dec 2020 17:09:11 -0500) 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:261023 Archived-At: > From: Stefan Monnier > Cc: stephen_leake@stephe-leake.org, daniele@grinta.net, emacs-devel@gnu.org > Date: Tue, 15 Dec 2020 17:09:11 -0500 > > What I'm suggesting is the following: > > - the tarball we build will include the same file as before in > `emacs/lisp`. > - it will additionally contain a new directory `emacs/elpa` in which > each bundled package has its own directory (all in the normal format > of installed packages in ~/.emacs.d/elpa). So we will have 2 copies of each package's Lisp files in the tarball? > So until `package-activate-all` is called, the bundled packages will > just sit there on your file system but Emacs won't "see" them. This already happens, right? we already call package-activate-all at startup, right? > We could also place some or all of the bundled packages directly inside > `lisp` Now I'm confused: how 'lisp/' is different from 'emacs/lisp' you mentioned above? > and have them be activated in the same way all other Emacs's code > is activated (i.e. basically by loading `loaddef.el` at dump time), so > they'll behave a bit less like normal packages and a bit more like Org > and Tramp do now (i.e. you can't "not have them"), but I think the above > suggestion is more conservative and flexible for the user (the downside > is that it's less efficient at startup). What are the pros and cons of each of these 2 alternatives? I think we should carefully consider them before deciding which one we prefer.