From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Adding AUCTeX to core Re: Why not include all ELPA packages in an Emacs release? Date: Sat, 08 Jun 2024 23:54:21 -0400 Message-ID: References: <87bk4ql3u5.fsf@jeremybryant.net> <864jagu9ji.fsf@gnu.org> <871q5ktxfh.fsf@posteo.net> <8734pzhzkh.fsf@jeremybryant.net> <874jafumc3.fsf@posteo.net> <87frtxhkp8.fsf@jeremybryant.net> <87sexo76s1.fsf@jeremybryant.net> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="16182"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: Jeremy Bryant , Philip Kaludercic , Andrea Corallo , Arash Esbati , Eli Zaretskii , Stefan Kangas , emacs-devel@gnu.org To: Po Lu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Jun 09 05:55:28 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 1sG9eS-00046C-0g for ged-emacs-devel@m.gmane-mx.org; Sun, 09 Jun 2024 05:55:28 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1sG9dX-0000NZ-5w; Sat, 08 Jun 2024 23:54:31 -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 1sG9dU-0000N4-H5 for emacs-devel@gnu.org; Sat, 08 Jun 2024 23:54:28 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sG9dS-0004cC-A5; Sat, 08 Jun 2024 23:54:28 -0400 Original-Received: from pmg1.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id EBD94100048; Sat, 8 Jun 2024 23:54:23 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1717905262; bh=jftGaZaK2/XVbW5O/fl+PMTsq61bsaZCMNdM4mlJN+g=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=oWtc88tnw4Tob/oVvrPHQsMx3WIG9TwGsj0uDAameNTXACR80lrLHfssdq4M0V2th Nr9wGxgqr4aAbKBLHMy1e3u0vs6/XEwHd7e58jVZtpCSMTkv+ZGLc964b9jfM3pET/ krCbBK/HZ/oujobfwQANR5gzxuwaVQeCAz4inFlDn80E19+bF0L0kLOe74woMTW/fy hiUw8GEr3SML7AqBl9DaaySdJn2ki1MnYwEEWLLaOkWL73qCTxapTxFZlbVH/Kp+Er WHofuPAMcHCgjDm+yRWTKpfczmbcMORgGqqfAUZ9SPtlZpR8KV8Ccj5Ssbhq1ryEa/ L6pelwfyFLtUQ== Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id D5F49100035; Sat, 8 Jun 2024 23:54:22 -0400 (EDT) Original-Received: from pastel (unknown [24.140.236.196]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 88D2B1203DA; Sat, 8 Jun 2024 23:54:22 -0400 (EDT) In-Reply-To: (Po Lu's message of "Sat, 08 Jun 2024 23:49:20 +0800") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, 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:319915 Archived-At: >> I really do want to see Emacs growing its build setup so it can bundle >> ELPA packages like AUCTeX. But that should not require any change on >> the part of AUCTeX. The benefit being that end users will get AUCTeX >> support without having to download and install the package. > This comes at the disadvantage of inconveniencing Emacs users who buikd > Emacs from the git repository, I don't see any reason to expect this would be any worse than what we have currently with all the other packages we have in core. And if an ELPA package fails to build, you can always re-set it to a previous commit, or build without ELPA packages. > unless AUCTeX take pains to coordinate with us, by, for instance, > designating versions that are "safe" for inclusion in Emacs, and > responding to reports of build failures and the like, which nullifies > the stated advantage to them. Telling us which versions are "safe" is already what maintainers do when they bump the version number, so it's not necessarily extra work. And it's much less work than sync'ing changes between two branches with unrelated history, like what the Org guys do, what the CEDET guys tried to do (and failed doing), what the Gnus guys did (and stopped doing at some point), what Alan does with CC-mode, etc... >> In comparison migrating AUCTeX into Emacs would require significant >> extra work on the part of AUCTeX with no extra benefit for the end >> users. > This extra work is invested once, Only if the `emacs.git` code becomes the one and only maintained code. Otherwise there's an on-going requirement to keep thr `emacs.git` code in-sync with some external branch without being able to use tools like `git merge`, so it's a rather unexciting manual work. > Meanwhile bundling ELPA packages in core remains a castle in the air, Very much so. > and its advantages and deficiencies are not nearly so absolute > or well-understood as it is implied. So please don't deal in absolutes. If I "dealt in absolutes" it was indeed a mistake. But I do know about the pain of keeping separate branches in sync and I want to provide a way to bundle packages without that extra pain. Nothing is a pure gain, so it'll come with its own compromises of course. Stefan