unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: [h-e-w] bug#10612: GnuTLS bundled with the windows Emacs	binaries
Date: Fri, 27 Jan 2012 09:59:53 -0600	[thread overview]
Message-ID: <87fwf13zly.fsf@lifelogs.com> (raw)
In-Reply-To: 83ty3iywh3.fsf@gnu.org

On Thu, 26 Jan 2012 23:39:36 +0200 Eli Zaretskii <eliz@gnu.org> wrote: 

>> I did offer to set up a BuildBot to produce those DLLs

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.  I will obviously make it
run the tests and if it fails, it will not deliver the DLLs.  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'm certainly not looking for
more work for myself, but it seems no one else wants to automate this.

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.

EZ> You (or anyone else) can find the prebuilt Windows binaries of
EZ> GnuTLS 3.0.9 here:
>> 
EZ> http://sourceforge.net/projects/ezwinports/files/
>> 
>> That's not what I asked, though I truly appreciate the work you've
>> done.  I mean if I, the user, see that announcement, it would be
>> nice if it told me where to find the GnuTLS DLLs, and even nicer if they
>> came with the binary.

EZ> The URLs for optional DLLs are in the file README.W32 that is part of
EZ> the binary distribution.

I'm asking *Christoph* if he could add that URL to the announcement for
the W32 binaries.  I think it would be a courtesy to the users.  I know
where to find the URL, but many users won't.

Ted




  reply	other threads:[~2012-01-27 15:59 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 [this message]
2012-01-27 15:30                     ` Juanma Barranquero
2012-01-30 12:59                       ` Ted Zlatanov
2012-01-27 15:45                     ` Eli Zaretskii
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=87fwf13zly.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --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).