unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: [h-e-w] bug#10612: GnuTLS bundled with the windows Emacs	binaries
Date: Fri, 27 Jan 2012 17:45:36 +0200	[thread overview]
Message-ID: <83aa59ywrj.fsf@gnu.org> (raw)
In-Reply-To: <87fwf13zly.fsf@lifelogs.com>

> From: Ted Zlatanov <tzz@lifelogs.com>
> Date: Fri, 27 Jan 2012 09:59:53 -0600
> 
> On Thu, 26 Jan 2012 23:39:36 +0200 Eli Zaretskii <eliz@gnu.org> 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.



  parent reply	other threads:[~2012-01-27 15:45 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <84boromyob.fsf@tum.de>
     [not found] ` <m3lipk5scv.fsf@stories.gnus.org>
     [not found]   ` <84ipknew07.fsf@tum.de>
     [not found]     ` <87ipjzs512.fsf@gnus.org>
2012-01-26 15:44       ` bug#10612: GnuTLS bundled with the windows Emacs binaries (was: bug#10215: 24.0.92; Can't contact nnimap (gnutls-cli not found)) Ted Zlatanov
2012-01-26 15:15         ` Juanma Barranquero
2012-01-26 19:32           ` bug#10612: GnuTLS bundled with the windows Emacs binaries Ted Zlatanov
2012-01-26 19:36             ` [h-e-w] " Eli Zaretskii
2012-01-26 21:07               ` Ted Zlatanov
2012-01-26 21:39                 ` Eli Zaretskii
2012-01-27 15:59                   ` Ted Zlatanov
2012-01-27 15:30                     ` Juanma Barranquero
2012-01-30 12:59                       ` Ted Zlatanov
2012-01-27 15:45                     ` Eli Zaretskii [this message]
2012-01-26 22:53                 ` Juanma Barranquero
2012-03-17 15:41           ` Uday S Reddy
2012-03-17 18:11             ` Eli Zaretskii
2012-03-22 18:38             ` Lars Magne Ingebrigtsen
2014-12-08 20:05           ` Lars Magne Ingebrigtsen
2014-12-08 20:31             ` Drew Adams
2014-12-08 20:50             ` Eli Zaretskii
2014-12-08 20:56               ` Lars Magne Ingebrigtsen
2014-12-08 21:10                 ` Óscar Fuentes
2014-12-08 21:24                   ` Lars Magne Ingebrigtsen
2016-02-05  7:28                 ` Lars Ingebrigtsen
2012-01-29 16:00         ` Christoph Scholtes
2012-01-29 16:47           ` Juanma Barranquero
2012-01-29 17:08             ` Christoph Scholtes
2012-01-29 17:26               ` Juanma Barranquero
2012-01-30  1:00                 ` Chong Yidong
2012-01-30 12:53                   ` Ted Zlatanov
2012-01-29 17:05           ` Eli Zaretskii
2012-01-30 13:07           ` Ted Zlatanov
2012-01-30 13:18             ` Juanma Barranquero

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83aa59ywrj.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).