From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Ted Zlatanov Newsgroups: gmane.emacs.devel Subject: Re: GnuTLS for W32 Date: Wed, 04 Jan 2012 18:16:26 -0500 Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @ Cienfuegos Message-ID: <87wr976otx.fsf@lifelogs.com> References: <874nwcu17i.fsf@wanadoo.es> <834nwcr6un.fsf@gnu.org> <87vcosskhc.fsf@wanadoo.es> <831urgr2yr.fsf@gnu.org> <87r4zgsh2w.fsf@wanadoo.es> <87ipks3zbo.fsf@uwakimon.sk.tsukuba.ac.jp> <87boqk3q69.fsf@uwakimon.sk.tsukuba.ac.jp> <87aa634st8.fsf@uwakimon.sk.tsukuba.ac.jp> <87fwfvsgfv.fsf@wanadoo.es> <877h17scdo.fsf@wanadoo.es> <87hb0b77nr.fsf@lifelogs.com> <8739bvs27m.fsf@wanadoo.es> <87ty4b4329.fsf@lifelogs.com> <87hb0b3yoe.fsf@lifelogs.com> <6ED011D5-E185-44C6-BB31-A445A4E5F83A@gmail.com> Reply-To: emacs-devel@gnu.org NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1325719013 5962 80.91.229.12 (4 Jan 2012 23:16:53 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Wed, 4 Jan 2012 23:16:53 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jan 05 00:16:49 2012 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Ria4c-0003kw-O8 for ged-emacs-devel@m.gmane.org; Thu, 05 Jan 2012 00:16:46 +0100 Original-Received: from localhost ([::1]:52137 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ria4c-0007LJ-0g for ged-emacs-devel@m.gmane.org; Wed, 04 Jan 2012 18:16:46 -0500 Original-Received: from eggs.gnu.org ([140.186.70.92]:44244) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ria4Z-0007LE-MB for emacs-devel@gnu.org; Wed, 04 Jan 2012 18:16:44 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Ria4Y-0002qx-Ct for emacs-devel@gnu.org; Wed, 04 Jan 2012 18:16:43 -0500 Original-Received: from lo.gmane.org ([80.91.229.12]:38116) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ria4Y-0002qi-0z for emacs-devel@gnu.org; Wed, 04 Jan 2012 18:16:42 -0500 Original-Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1Ria4U-0003gE-QT for emacs-devel@gnu.org; Thu, 05 Jan 2012 00:16:38 +0100 Original-Received: from c-76-28-40-19.hsd1.vt.comcast.net ([76.28.40.19]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 05 Jan 2012 00:16:38 +0100 Original-Received: from tzz by c-76-28-40-19.hsd1.vt.comcast.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 05 Jan 2012 00:16:38 +0100 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: emacs-devel@gnu.org Original-Lines: 37 Original-X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: c-76-28-40-19.hsd1.vt.comcast.net User-Agent: Gnus/5.110018 (No Gnus v0.18) Emacs/24.0.90 (gnu/linux) X-Face: bd.DQ~'29fIs`T_%O%C\g%6jW)yi[zuz6; d4V0`@y-~$#3P_Ng{@m+e4o<4P'#(_GJQ%TT= D}[Ep*b!\e,fBZ'j_+#"Ps?s2!4H2-Y"sx" Mail-Copies-To: never Cancel-Lock: sha1:xm19G+Czm2Y3U9GazKYmD3bfXEo= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-Received-From: 80.91.229.12 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 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-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:147302 Archived-At: On Wed, 4 Jan 2012 14:47:02 -0800 chad wrote: c> I have a suggestion: by policy put the DLLs with the binary, make the c> installer DTRT, and then add some sort of `update alert' facility c> that checks ELPA to notify users about new versions. This facility c> would not necessarily update the software itself, but would notify c> users that a new version of the software exists, along with notes c> about the changes (especially the severity of the changes) and c> instructions for updating. The installer-based default would only c> (somehow) bug the user about severe problems (such as security c> breaches for GnuTLS), pointing them at a new installer. Users who c> opted in could be notified of all changes (perhaps displaying c> ChangeLogs or vc status messages at the far end). I really like your suggestion. It lets us write the DLL deployment code later or never, depending on what users want, but at first we will only do the acceptable minimum. It can also work with a standalone GnuTLS W32 installer, if we ever decide that's a better approach. GnuTLS provides gnutls_check_version() which we can use to dynamically find out the version of the currently loaded GnuTLS DLL, by calling it with a NULL. So the package's version check should be fairly easy to write, and its version string will simply match the GnuTLS release it's tracking. I think, to get this working, we need a list of critical ELPA packages that Emacs will check for updates on startup and alert the user to upgrade. By default that list should be empty on all platforms, except on W32 it will contain the "gnutls-w32" package. The actual package will have to live on the GNU ELPA site, so that will require a network connection to be opened... this will almost certainly displease some Emacs users if we make it a default, but I do think it's the right one. As a user I would like to have such a list, and will probably add a few packages to it for my personal use. Ted