From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Jeremy Bryant Newsgroups: gmane.emacs.devel Subject: Moving core packages to ELPA [Was: Re: Why not include all ELPA packages in an Emacs release?] Date: Fri, 07 Jun 2024 22:48:25 +0100 Message-ID: <871q588lw6.fsf@jeremybryant.net> References: <87bk4ql3u5.fsf@jeremybryant.net> <864jagu9ji.fsf@gnu.org> <86bk4nsx6k.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="7301"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Stefan Kangas , emacs-devel@gnu.org, monnier@iro.umontreal.ca, philipk@posteo.net To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Jun 07 23:49:08 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 1sFhSN-0001gz-CI for ged-emacs-devel@m.gmane-mx.org; Fri, 07 Jun 2024 23:49:07 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1sFhRq-0001mr-Tn; Fri, 07 Jun 2024 17:48:34 -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 1sFhRp-0001mR-Ba for emacs-devel@gnu.org; Fri, 07 Jun 2024 17:48:33 -0400 Original-Received: from out-173.mta1.migadu.com ([2001:41d0:203:375::ad]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sFhRn-0001pp-GJ for emacs-devel@gnu.org; Fri, 07 Jun 2024 17:48:33 -0400 X-Envelope-To: philipk@posteo.net DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jeremybryant.net; s=key1; t=1717796908; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=96GCbvSy1oPUwLvMVv9vogJB0Ah/Ml/BaWDccLXFf58=; b=l9SNuGHJfo+h+5CS6WrirhYJUEU8NVFhPGVAaoWRmrTh4bPtIsSskUP7G2xj7k1V1qFirU efSfgLh1c/qMj0BzM8rqHDkxQulpILnFsfoLvRmsr97r4Hh5bgbdn7E88CnsGvlGHFpmBo v7CRCUKXqdMZAQ0TTJzEQHaxAszlBEI58liIQS7SVxHNE5HRIpB/XkiURigqntI2lfnQ65 cHq0/eVRblteiRfAhdY8ALQfU+ruBVoHm0miYebjttmqsYuE3+w/rR6tep+WMe/5WC6K74 ds9X+smo2qa4W3Yo+faxzfkCWcrLgz3pkQaaqDTmXhtHusOZoJ+wc+5xx3K83A== X-Envelope-To: monnier@iro.umontreal.ca X-Envelope-To: emacs-devel@gnu.org X-Envelope-To: stefankangas@gmail.com X-Envelope-To: eliz@gnu.org X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. In-Reply-To: <86bk4nsx6k.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 30 May 2024 08:09:23 +0300") X-Migadu-Flow: FLOW_OUT Received-SPF: pass client-ip=2001:41d0:203:375::ad; envelope-from=jb@jeremybryant.net; helo=out-173.mta1.migadu.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_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=unavailable 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:319871 Archived-At: Eli Zaretskii writes: >> From: Stefan Kangas >> Date: Wed, 29 May 2024 13:44:37 -0700 >> Cc: jb@jeremybryant.net, emacs-devel@gnu.org, monnier@iro.umontreal.ca, >> philipk@posteo.net >> >> Eli Zaretskii writes: >> >> > What we discussed was the desire to move packages out of core in a way >> > that a release tarball would include those package. That is what we >> > have a consensus about (but not a complete and satisfactory solution >> > yet). >> >> It's possible that we have interpreted the previous discussions a bit >> differently, or that I'm filling in too many blanks. >> >> My understanding was that this was always going to be something like >> 1) make it possible to ship ELPA packages with core Emacs and then >> 2) decide which packages should be included. >> >> To my mind, step 2 could either be restricted to only include packages >> that used to be in core, or it could not be. The difference is not very >> big, at least not in principle, since before we bundle even two >> packages, we still have to solve the issue of how to bundle even one. > > Sure, but we never meant that step 2 will include all of ELPA, I > think. And at least my understanding of step 2 was indeed that it > should allow to have more core packages on ELPA than to add packages > to the Emacs release tarballs. What is a good core package to start working on migrating to ELPA? (In searching previous discussions, it wasn't obvious, apart from IDLWAVE)