From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Hotfixing older Emacsen? Was: [ANNOUNCE] Emacs 25.3 released Date: Mon, 18 Sep 2017 07:38:36 -0400 Message-ID: References: <87wp55t0un.fsf@petton.fr> <87mv5sh2gz.fsf@petton.fr> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1505734773 19338 195.159.176.226 (18 Sep 2017 11:39:33 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 18 Sep 2017 11:39:33 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.0.50 (gnu/linux) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Sep 18 13:39:26 2017 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dtuOc-0004hf-GO for ged-emacs-devel@m.gmane.org; Mon, 18 Sep 2017 13:39:26 +0200 Original-Received: from localhost ([::1]:35851 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dtuOj-0001r1-PD for ged-emacs-devel@m.gmane.org; Mon, 18 Sep 2017 07:39:33 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:40824) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dtuO5-0001qu-L1 for emacs-devel@gnu.org; Mon, 18 Sep 2017 07:38:55 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dtuO2-0004Wr-J7 for emacs-devel@gnu.org; Mon, 18 Sep 2017 07:38:53 -0400 Original-Received: from [195.159.176.226] (port=47481 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dtuO2-0004Vm-C2 for emacs-devel@gnu.org; Mon, 18 Sep 2017 07:38:50 -0400 Original-Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1dtuNs-0002j1-HW for emacs-devel@gnu.org; Mon, 18 Sep 2017 13:38:40 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 17 Original-X-Complaints-To: usenet@blaine.gmane.org Cancel-Lock: sha1:nXGNc1ePMaZlBmWXd0ASN3OK0mQ= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 195.159.176.226 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 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.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:218454 Archived-At: >> > Crazy though: why don't we hot-patch existing Emacs installations? >> > Concretely, that would mean including that fix in a widely used ELPA >> > or MELPA package. Then users would get the fix upon the next update. >> This verges on a universal back door, aka "auto-upgrade" >> which is a form of malware normally found in proprietary software. > What if the user was asked for a confirmation before upgrading? > Would that be a good solution? I think fixes should be in a separate package. If we really feel it's necessary, we could consider adding some code to some unrelated popular package which could do something like: - look for known bugs (fixed in security-patches) - if found some, tell the user, suggesting to install the security-patches package -- Stefan