unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: emacs-devel@gnu.org
Subject: Re: Win32 GnuTLS DLL installer?
Date: Thu, 21 Sep 2017 20:44:05 +0300	[thread overview]
Message-ID: <83a81odk0q.fsf@gnu.org> (raw)
In-Reply-To: <87vakcc5xn.fsf@lifelogs.com> (message from Ted Zlatanov on Thu,  21 Sep 2017 13:33:40 -0400)

> From: Ted Zlatanov <tzz@lifelogs.com>
> Date: Thu, 21 Sep 2017 13:33:40 -0400
> 
> EZ> So whenever the current branch sees a new release, someone would have
> EZ> to port it to Windows and provide the binaries?
> 
> I'd check for the binaries that are actually available, so it wouldn't
> do anything other than saying "hey there's a new DLL you should run."

Available from where?  Surely, we won't want to recommend
security-related DLLs whose quality we cannot guarantee, would we?
And how can we guarantee quality of DLLs built by someone out there,
about whose build procedure and its QA we know nothing?  E.g., how do
we know they've run the test suite and made sure every failure is
either fixed or analyzed to conclude that it isn't a real problem?

Bottom line, I'd really love to see someone volunteer to do this job
in a way that we could simply rely on them and point to their site (or
copy stuff from there to ELPA), but I'm not holding my breath, having
done that several times myself.  It's not an easy job, and requires
non-trivial investment of time and effort.



  reply	other threads:[~2017-09-21 17:44 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-20 16:08 Win32 GnuTLS DLL installer? Ted Zlatanov
2017-09-20 20:15 ` Phillip Lord
2017-09-21  2:52   ` Sivaram Neelakantan
2017-09-21 11:19   ` Eli Zaretskii
2017-09-21 20:23     ` Phillip Lord
2017-09-21 14:28   ` Ted Zlatanov
2017-09-21 14:49     ` Eli Zaretskii
2017-09-21 15:38       ` Ted Zlatanov
2017-09-21 16:58         ` Eli Zaretskii
2017-09-21 17:33           ` Ted Zlatanov
2017-09-21 17:44             ` Eli Zaretskii [this message]
2017-09-21 17:57               ` Ted Zlatanov
2017-09-21 18:31                 ` Eli Zaretskii
2017-09-21 21:16                   ` Phillip Lord
2017-09-22  7:29                     ` Eli Zaretskii
2017-09-21 21:13                 ` Phillip Lord
2017-09-21 21:08         ` Phillip Lord
2017-09-22 12:44           ` Ted Zlatanov
2017-09-27  8:57   ` Jostein Kjønigsen
2017-11-20 19:41     ` Ted Zlatanov
2017-11-22 23:11       ` Phillip Lord

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=83a81odk0q.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=tzz@lifelogs.com \
    /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).