From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Ted Zlatanov Newsgroups: gmane.emacs.devel,gmane.emacs.windows Subject: Re: Emacs 24.0.93 Pretest Windows Binaries published Date: Thu, 02 Feb 2012 16:46:17 -0500 Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @ Cienfuegos Message-ID: <877h04nc2e.fsf@lifelogs.com> References: <4F25FA2F.2010401@gmail.com> <4F27F4A1.6030907@gmail.com> <6E4BE1E758D04283A7C3A660ED379966@us.oracle.com> <87liolnipl.fsf@lifelogs.com> <50081AA79F2F4860A3B9DCEDFC1ABEC8@us.oracle.com> Reply-To: emacs-devel@gnu.org NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1328219205 4537 80.91.229.3 (2 Feb 2012 21:46:45 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 2 Feb 2012 21:46:45 +0000 (UTC) Cc: help-emacs-windows@gnu.org To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Feb 02 22:46:44 2012 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Rt4UL-00015S-DA for ged-emacs-devel@m.gmane.org; Thu, 02 Feb 2012 22:46:41 +0100 Original-Received: from localhost ([::1]:58358 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Rt4UK-000716-Km for ged-emacs-devel@m.gmane.org; Thu, 02 Feb 2012 16:46:40 -0500 Original-Received: from eggs.gnu.org ([140.186.70.92]:40264) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Rt4UD-00070Q-Nu for emacs-devel@gnu.org; Thu, 02 Feb 2012 16:46:38 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Rt4UC-0007Bh-60 for emacs-devel@gnu.org; Thu, 02 Feb 2012 16:46:33 -0500 Original-Received: from plane.gmane.org ([80.91.229.3]:51589) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Rt4UB-0007Bb-UM for emacs-devel@gnu.org; Thu, 02 Feb 2012 16:46:32 -0500 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1Rt4U9-00010D-W0 for emacs-devel@gnu.org; Thu, 02 Feb 2012 22:46:30 +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, 02 Feb 2012 22:46:29 +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, 02 Feb 2012 22:46:29 +0100 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: emacs-devel@gnu.org Original-Lines: 59 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.130002 (Ma Gnus v0.2) Emacs/24.0.93 (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:orj4Ui1y7eMaz3cEa6EVAyUMEzU= X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 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:148135 gmane.emacs.windows:5262 Archived-At: On Thu, 2 Feb 2012 11:52:25 -0800 "Drew Adams" wrote: DA> The readme is the only place we mention other Windows DA> binaries - e.g. image binaries. Why treat GnuTLS specially? DA> Either mention GnuTLS only in the readme (preferred) DA> or mention in the announcement each of the binaries DA> that mentioned in the readme (not preferred). >> >> I requested that GnuTLS be treated specially. I believe this is >> necessary because it's important for secure networking on W32, unlike >> any of the other libraries. This is a temporary remedy; I >> will work on a W32 installer and then it won't be necessary >> to mention GnuTLS explicitly (a link to the installer in the >> announcement would be sufficient). DA> 1. According to Eli, "It's an email authentication package." Which would mean DA> that it is needed only by people who use Emacs for email. DA> At a minimum, that should be pointed out in the brief description that needs to DA> accompany this "special treatment". DA> And that's the case wherever we choose to describe GnuTLS. (And it should be DA> described in the README, irregardless of whether it is described in the DA> announcement.) GnuTLS provides SSL and TLS encryption for any network connection, hence "secure networking" in my earlier message. It can encrypt e-mail protocols like IMAP and SMTP but does not deal with e-mail messages. DA> 2. I'm not familiar with your proposed "installer", but I certainly hope that we DA> will continue to distribute a simple zip archive with a Windows binary. DA> A priori, I for one will not use an installer to "install" the binary. I use DA> multiple Emacs Windows binaries, and I do not need an Emacs installer mucking DA> about with my registry etc. This is one reason I do not use Lennart's DA> installer, for instance. DA> It is blindingly simple for a user to unzip an archive in a directory of choice, DA> and create a startup shortcut. Nothing to it. DA> What's the motivation for this installer? I can understand Lennart's DA> motivation, since he has apparently customized many things, including at the C DA> level. But why do you think Emacs users on Windows need an installer for DA> vanilla Emacs? DA> I have nothing against the general idea of our providing an installer in DA> _addition_ to our providing zip archives, but I would not want to see the latter DA> practice dropped. Any installer I assemble will not replace the Emacs binaries and will not be as "official" as Christoph's binaries. It will not involve emacs-devel resources, at least. I've covered the reasons for the installer on this list, going back and forth over several alternatives. This was a very recent thread. An installer seems to be the best approach but you can read through the discussion and decide for yourself. Ted