From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: [h-e-w] bug#10612: GnuTLS bundled with the windows Emacs binaries Date: Fri, 27 Jan 2012 17:45:36 +0200 Message-ID: <83aa59ywrj.fsf@gnu.org> References: <84boromyob.fsf@tum.de> <84ipknew07.fsf@tum.de> <87ipjzs512.fsf@gnus.org> <87wr8e8o58.fsf_-_@lifelogs.com> <87ipjy6z0j.fsf@lifelogs.com> <83zkdaz26s.fsf@gnu.org> <8739b26ume.fsf@lifelogs.com> <83ty3iywh3.fsf@gnu.org> <87fwf13zly.fsf@lifelogs.com> Reply-To: Eli Zaretskii NNTP-Posting-Host: lo.gmane.org X-Trace: dough.gmane.org 1327679273 817 80.91.229.12 (27 Jan 2012 15:47:53 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Fri, 27 Jan 2012 15:47:53 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jan 27 16:47:48 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 1Rqo1j-0007GA-O3 for ged-emacs-devel@m.gmane.org; Fri, 27 Jan 2012 16:47:48 +0100 Original-Received: from localhost ([::1]:33569 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Rqo1j-0007od-8J for ged-emacs-devel@m.gmane.org; Fri, 27 Jan 2012 10:47:47 -0500 Original-Received: from eggs.gnu.org ([140.186.70.92]:34247) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Rqo1g-0007oX-Ff for emacs-devel@gnu.org; Fri, 27 Jan 2012 10:47:45 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Rqo1e-0007Uv-Ov for emacs-devel@gnu.org; Fri, 27 Jan 2012 10:47:44 -0500 Original-Received: from mtaout20.012.net.il ([80.179.55.166]:46849) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Rqo1e-0007Um-Gx for emacs-devel@gnu.org; Fri, 27 Jan 2012 10:47:42 -0500 Original-Received: from conversion-daemon.a-mtaout20.012.net.il by a-mtaout20.012.net.il (HyperSendmail v2007.08) id <0LYG00700RUBM900@a-mtaout20.012.net.il> for emacs-devel@gnu.org; Fri, 27 Jan 2012 17:47:40 +0200 (IST) Original-Received: from HOME-C4E4A596F7 ([84.228.102.195]) by a-mtaout20.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0LYG007HMRVELO20@a-mtaout20.012.net.il> for emacs-devel@gnu.org; Fri, 27 Jan 2012 17:47:39 +0200 (IST) In-reply-to: <87fwf13zly.fsf@lifelogs.com> X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: Solaris 10 (beta) X-Received-From: 80.179.55.166 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:147983 Archived-At: > From: Ted Zlatanov > Date: Fri, 27 Jan 2012 09:59:53 -0600 > > On Thu, 26 Jan 2012 23:39:36 +0200 Eli Zaretskii wrote: > > EZ> How can anyone trust a build done by a bot for a port to a platform > EZ> that is hardly if at all supported by the mainstream developers? And > EZ> a build of critical software such as GnuTLS at that? What if it fails > EZ> one of the tests in the test suite? > > Someone has to do the work. I offered to do it, setting up a BuildBot > so I don't have to do it manually every time. The build itself is not where most of the efforts need to be invested. It's the careful examination of any compiler and linker warnings and test suite results that takes most of the time. That, and the need to refresh the packages that are prerequisites (at least 4 are required), each one of which has its own share of quirks and problems. > I will obviously make it run the tests and if it fails, it will not > deliver the DLLs. Then I think you will never deliver. E.g., my perfectly good build failed 3 times in the test suite, due to problems in the test suite itself. I would expect at least one test to fail with each new release. > Do you have a better proposal (e.g. you want to be in charge of the > builds or you know volunteers who want to do it)? I don't know what it means to be "in charge". I did the port of 3.0.9, and I can refresh it from time to time, as my time permits. I cannot make any promises, and I certainly cannot produce a fresh port every 2 weeks. If some grave problem gets detected in the last port, and someone reports that a new version fixes that, I could try doing a quick port of that. If that's good enough, this part is covered; if not, someone else will have to do it. > I'm certainly not looking for more work for myself, but it seems no > one else wants to automate this. As I said, automation is not the issue (how hard is it to type the 3 commands, including "make install-strip", needed to produce a new set of binaries?). But feel free to set it up, maybe I'm wrong and the problem is not as complicated as I think it is. > The fact that the GnuTLS developers don't support W32 well is partly due > to the lack of binary builds for that platform. I think things will > improve as up-to-date DLLs become available. Well, they are available now, but I see no change, at least not judging by the traffic on the mailing list.