From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Win32 GnuTLS DLL installer? Date: Thu, 21 Sep 2017 17:49:32 +0300 Message-ID: <83mv5ods3n.fsf@gnu.org> References: <87lgl9e4ji.fsf@lifelogs.com> <5e2a6b84f4051ba2d4d427200045c947.squirrel@cloud103.planethippo.com> <8760ccdt3g.fsf@lifelogs.com> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1506005450 11817 195.159.176.226 (21 Sep 2017 14:50:50 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Thu, 21 Sep 2017 14:50:50 +0000 (UTC) Cc: emacs-devel@gnu.org To: Ted Zlatanov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Sep 21 16:50:43 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 1dv2oJ-0002Sa-7G for ged-emacs-devel@m.gmane.org; Thu, 21 Sep 2017 16:50:39 +0200 Original-Received: from localhost ([::1]:54076 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dv2oQ-0003kr-Ik for ged-emacs-devel@m.gmane.org; Thu, 21 Sep 2017 10:50:46 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:54419) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dv2nS-0003jG-Ck for emacs-devel@gnu.org; Thu, 21 Sep 2017 10:49:47 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dv2nO-0006Fb-Ds for emacs-devel@gnu.org; Thu, 21 Sep 2017 10:49:46 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:35616) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dv2nO-0006FT-AJ; Thu, 21 Sep 2017 10:49:42 -0400 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:1639 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1dv2nN-0003kR-9r; Thu, 21 Sep 2017 10:49:42 -0400 In-reply-to: <8760ccdt3g.fsf@lifelogs.com> (message from Ted Zlatanov on Thu, 21 Sep 2017 10:28:03 -0400) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e 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:218635 Archived-At: > From: Ted Zlatanov > Date: Thu, 21 Sep 2017 10:28:03 -0400 > > (A possible use case for the security-patches package/repo/mechanism > could be to check the DLL version and notify the user if it's outdated. How do you define "outdated"? GnuTLS developers maintain 3 branches in parallel, and release versions from all the 3 branches. Which one should we follow, and does any N+1 release from that branch mean that the N release is considered "outdated" and should be replaced? Moreover, accommodating a new version of GnuTLS might mean changes to Emacs C and/or Lisp sources -- are we going to release patches to the core sources through ELPA or something? IOW, this sounds like a major undertaking on our part, and I'm sure more and more issues will pop up as we consider the implications. I'm not sure we want to become a de-facto "distro" for MS-Windows users, as I don't think we have the resources, even if we have the desire.