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: Suppressing native compilation (short and long term) Date: Sun, 02 Oct 2022 19:55:24 +0300 Message-ID: <83edvq17yb.fsf@gnu.org> References: <87bkqxf1ij.fsf@tethera.net> <8335c9dkyf.fsf@gnu.org> <83tu4odez7.fsf@gnu.org> <871qrrpkgx.fsf@trouble.defaultvalue.org> <834jwnbi6c.fsf@gnu.org> <87mtafnun5.fsf@trouble.defaultvalue.org> <83sfk6ahty.fsf@gnu.org> <83czbaafnj.fsf@gnu.org> <83ill21adr.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="23669"; mail-complaints-to="usenet@ciao.gmane.io" Cc: tomas@tuxteam.de, emacs-devel@gnu.org To: chad Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Oct 02 18:56:10 2022 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 1of2GA-0005yC-ON for ged-emacs-devel@m.gmane-mx.org; Sun, 02 Oct 2022 18:56:10 +0200 Original-Received: from localhost ([::1]:55580 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1of2G9-0005Bw-OZ for ged-emacs-devel@m.gmane-mx.org; Sun, 02 Oct 2022 12:56:09 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:35514) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1of2FY-0004TR-Gj for emacs-devel@gnu.org; Sun, 02 Oct 2022 12:55:32 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:35932) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1of2FY-0000n5-6X; Sun, 02 Oct 2022 12:55:32 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=81RcGpmqRLs38gVhA2wuKkkV11nRPTlXjP448DQJTF4=; b=C2Txh6/8hTg1 97OUGUp++TdL2DA7Sd5/eG6WkqhJ+emduBtK3tHlYcakuVz4ntm8OoWlil3I7hw9wNE/0AF8MNjYx chNewzD26T34Iv/dU3CGRUBycam3zyDBCUE3FzccBUK4ioPSOPesrGcKQkwZ3jSGTG5IDEJabK7Go VkNdoDl+dPXxiR5ckYIvDYLrIdP991cJo5fhbPoGCvraW4kcYnepeTr6UQe7troAry5AR8QsDB3wk nGUgOvKP77W1xNm9Evx5v296fXoe3uiZEzfAJopuI/PU06TPxeo1lOFF5vusufjW0AJcYRPu68icK O1NZNoYXg/tX+Dbb6RBVow==; Original-Received: from [87.69.77.57] (port=2278 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1of2FX-0005hB-IN; Sun, 02 Oct 2022 12:55:31 -0400 In-Reply-To: (message from chad on Sun, 2 Oct 2022 12:13:44 -0400) 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" Xref: news.gmane.io gmane.emacs.devel:296642 Archived-At: > From: chad > Date: Sun, 2 Oct 2022 12:13:44 -0400 > Cc: tomas@tuxteam.de, emacs-devel@gnu.org > > > Ah, I see. I was too sloppy. I was talking about Debian packages. > > That still doesn't explain it to me (I don't use Debian). Can you > elaborate what kind of packages are we talking about, in the context > of this discussion? > > Debian supports a user installing, for example, emacs+magit, via Debian packages. This gets the user a > stable, known-tested version of emacs plus the package usable on machines that, for another example, > cannot or should not connect to the internet. This is less important to developers, but is an important part of > the Debian support "contract". Which part of the "emacs+magit" package is the "binary package"? The only part of that which could produce *.eln files at installation time is Magit, right? Because Emacs itself already comes with all the preloaded *.eln files, and those aren't what we are talking about, right? And if we are talking about Magit in this example, then how come its being bundled to Emacs change anything of what I said? > For the record: I personally know of situations where such a setup would like to use native-comp and would > very much prefer NOT to duplicate either the eln files per-user nor the effort of creating such. Whether or > not that situation is important enough to the combination of emacs-devel and debian-maintainers to justify > effort on either side is, of course, debatable, but I am highly confident that they exist (at least, did before the > pandemic). Please forgive me, but you cannot expect us to regard such situations seriously as long as you don't describe them.