From: Eli Zaretskii <eliz@gnu.org>
To: Lars Magne Ingebrigtsen <larsi@gnus.org>
Cc: help-emacs-windows@gnu.org, lekktu@gmail.com,
emacs-devel@gnu.org, 10612@debbugs.gnu.org
Subject: Re: bug#10612: GnuTLS bundled with the windows Emacs binaries
Date: Mon, 08 Dec 2014 22:50:41 +0200 [thread overview]
Message-ID: <83388pyify.fsf@gnu.org> (raw)
In-Reply-To: <m3ppbtsy9z.fsf@stories.gnus.org>
> From: Lars Magne Ingebrigtsen <larsi@gnus.org>
> Date: Mon, 08 Dec 2014 21:05:12 +0100
> Cc: 10612@debbugs.gnu.org, emacs-devel@gnu.org, help-emacs-windows@gnu.org
>
> Juanma Barranquero <lekktu@gmail.com> writes:
>
> > Note (again) that the issue is not who builds the GnuTLS DLLs, but
> > whether they should be included with official (or semi-official, like
> > the snapshots) releases.
>
> Does the new semi-official build include the GnuTLS DLLs? It seems to
> include a lot of the other libraries, but it doesn't mention GnuTLS...
It doesn't include any DLLs except libXpm (which is needed for the
tool-bar icons). It was built with GnuTLS, though, so if the end user
installs GnuTLS, Emacs will find it and use it.
(We never distributed Windows DLLs with Emacs, because that would
require us to host their sources, their dependencies, and the sources
of their dependencies on ftp.gnu.org, which IIRC raises all kinds of
questions and issues with their licenses.)
next prev parent reply other threads:[~2014-12-08 20:50 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
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 [this message]
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=83388pyify.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=10612@debbugs.gnu.org \
--cc=emacs-devel@gnu.org \
--cc=help-emacs-windows@gnu.org \
--cc=larsi@gnus.org \
--cc=lekktu@gmail.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).