From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Philip Kaludercic Newsgroups: gmane.emacs.devel Subject: Re: Why not include all ELPA packages in an Emacs release? Date: Wed, 29 May 2024 05:59:36 +0000 Message-ID: <87jzjd5fav.fsf@posteo.net> References: <87bk4ql3u5.fsf@jeremybryant.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="34986"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Jeremy Bryant , Emacs Devel , Stefan Monnier To: Stefan Kangas Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed May 29 08:00:39 2024 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 1sCCMZ-0008vs-NG for ged-emacs-devel@m.gmane-mx.org; Wed, 29 May 2024 08:00:39 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1sCCLj-0002g0-3l; Wed, 29 May 2024 01:59:47 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sCCLg-0002ed-Cj for emacs-devel@gnu.org; Wed, 29 May 2024 01:59:44 -0400 Original-Received: from mout01.posteo.de ([185.67.36.65]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sCCLe-0002AE-CZ for emacs-devel@gnu.org; Wed, 29 May 2024 01:59:44 -0400 Original-Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id 29C75240027 for ; Wed, 29 May 2024 07:59:38 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1716962379; bh=6joiA2BVap4PZ8F+mG7j4icIwuv1wuR2BN2Za8dnxog=; h=From:To:Cc:Subject:OpenPGP:Date:Message-ID:MIME-Version: Content-Type:Content-Transfer-Encoding:From; b=C3dKGP9VMvMduHpCHwn/kbvVt0w4RokIr2nrIB8jNVyu55vGimKUNP5VSMzbnsUrI o7nDgdyBel0zoFsteyIVMAqLX7EF7dKKJNVKMp7GWVOluSmGSL/K9qi81yvMw467xX s8Lz8z42YkK6pC4pJjJI7FKvijPK7uqb6WVDJAlmH9ag9Eck19WCDBsguB0hmmUfQh fXTQwt5ouUmiCxN75QZJG0eeQb1fl0uuwV65qE9SoRekPQfTTzkHj1JDMs8kl61BLv DECOeuib6yh/fcMy3Jjt/w0FjROVzlDd22RUlgvrT565JxkbUCSeL6DgxHwXPzDnPo 8sDl6a6B1x2rA== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4VpzHF15gNz9rxN; Wed, 29 May 2024 07:59:36 +0200 (CEST) In-Reply-To: (Stefan Kangas's message of "Tue, 28 May 2024 23:15:49 +0000") OpenPGP: id=7126E1DE2F0CE35C770BED01F2C3CC513DB89F66; url="https://keys.openpgp.org/vks/v1/by-fingerprint/7126E1DE2F0CE35C770BED01F2C3CC513DB89F66"; preference=signencrypt Received-SPF: pass client-ip=185.67.36.65; envelope-from=philipk@posteo.net; helo=mout01.posteo.de X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 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, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:319669 Archived-At: Stefan Kangas writes: > Jeremy Bryant writes: > >> Would there be a problem in including a snapshot of ELPA packages in an >> Emacs release? > > This has been discussed several times in the past. There are no > principal problems, and AFAIU the consensus is that we would like to > do it, though there are some practical issues to work out. > > I believe if you search the list archives, you will find previous > discussions that will shed some light on the issues involved. We can't > just dump all packages in lisp/ and be done with it, unfortunately. > > I honestly can't cite all of the problems off the top of my head.=20=20 I have bookmarked this message by Eli, where he links to a few threads with issues that should be dealt with: <83zg27emh8.fsf@gnu.org> > One > is how we track developments on GNU ELPA, if we mirror packages into > emacs.git, or if we add them as submodules, or what. At the very least, > we'd probably need to have some record of what we put into the release > tarball. Do we add _all_ packages or just some subset? Should they be > registered in `package--builtins=C2=B4, and how? Should they be part of = the > main release tarball, or released separately? And so on. > > Mostly, we need an interested volunteer to step up and do the work. > This would probably start with reviewing past discussions to find out > what problems they uncovered. Then propose, in practical terms, how we > could solve them. > > So help is both welcome and needed here, I think. --=20 Philip Kaludercic on peregrine