From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: =?utf-8?Q?=C3=93scar_Fuentes?= Newsgroups: gmane.emacs.devel Subject: Re: Merging MPS a.k.a. scratch/igc, yet again Date: Tue, 10 Dec 2024 14:10:57 +0100 Message-ID: <87ldwnn0ny.fsf@telefonica.net> References: <878qwuitbu.fsf@yahoo.com> <87jzcajrnz.fsf@protonmail.com> <86o71mfhox.fsf@gnu.org> <87frmyjn9j.fsf@protonmail.com> <86ldwqfcqv.fsf@gnu.org> <87a5d6jgim.fsf@protonmail.com> <86a5d6f7bn.fsf@gnu.org> <871pyijctd.fsf@protonmail.com> <8634iyf257.fsf@gnu.org> <8634iwex8q.fsf@gnu.org> <87plm0msrq.fsf@telefonica.net> <87zfl4npcd.fsf@debian-hx90.lan> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="3689"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) To: emacs-devel@gnu.org Cancel-Lock: sha1:lTHcWv+D81fsIIaZYAFrpkyPx7A= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Dec 10 14:51:23 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 1tL0e1-0000rS-N8 for ged-emacs-devel@m.gmane-mx.org; Tue, 10 Dec 2024 14:51:21 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tL0dU-0004H1-Df; Tue, 10 Dec 2024 08:50:48 -0500 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 1tL018-0002gi-OY for emacs-devel@gnu.org; Tue, 10 Dec 2024 08:11:11 -0500 Original-Received: from ciao.gmane.io ([116.202.254.214]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tL013-0008Kx-8o for emacs-devel@gnu.org; Tue, 10 Dec 2024 08:11:10 -0500 Original-Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1tL010-0000dJ-TS for emacs-devel@gnu.org; Tue, 10 Dec 2024 14:11:02 +0100 X-Injected-Via-Gmane: http://gmane.org/ Received-SPF: pass client-ip=116.202.254.214; envelope-from=ged-emacs-devel@m.gmane-mx.org; helo=ciao.gmane.io X-Spam_score_int: -15 X-Spam_score: -1.6 X-Spam_bar: - X-Spam_report: (-1.6 / 5.0 requ) BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action X-Mailman-Approved-At: Tue, 10 Dec 2024 08:50:47 -0500 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:326287 Archived-At: Xiyue Deng writes: > If making MPS available in Debian would help Emacs packaging I'm willing > to work on this (in the coming weeks as igc may not land with the > upcoming Emacs 30 release so not in a hurry.) As a Debian user, I value every package that is made available through its repos, thank you. However, in the specific case of Emacs/MPS, IMAO distro packaging is not the best way, because: * Depending on packaged MPS brings versioning problems, not to mention that it would take a long time to have MPS available on a large part of the distro ecosystem. We would need the DIY part of README-IGC anyway. * It is very likely that we end doing some patching to the MPS sources to adapt to our specific needs (if those patches end upstream or not, that's another question.) * MPS does a performance-critical job. Using it as a shared object might incur in a performance penalty. Having it in source form alongside the Emacs sources will result in opportunities for optimizations (LTO, PGO, ...) that may bring better performance. * MPS does a correctness-critical job. Depending on multiple external sources for such core component is a recipe for problems (future changes by the MPS maintainers, patching by packagers, buggy compilers, etc.) We need to keep a close watch on what MPS incarnation we use. Better yet, total control. For those reasons, incorporating MPS into the Emacs sources is the right thing to do.