unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Christoph Scholtes <cschol2112@googlemail.com>
To: Emacs-Devel devel <emacs-devel@gnu.org>, Ted Zlatanov <tzz@lifelogs.com>
Cc: Juanma Barranquero <lekktu@gmail.com>, Eli Zaretskii <eliz@gnu.org>
Subject: Re: bug#10612: GnuTLS bundled with the windows Emacs binaries
Date: Sun, 29 Jan 2012 09:00:30 -0700	[thread overview]
Message-ID: <4F256D1E.4070902@gmail.com> (raw)
In-Reply-To: <87wr8e8o58.fsf_-_@lifelogs.com>

Ted,

On 1/26/2012 8:44 AM, Ted Zlatanov wrote:

> Christoph, can you add a GnuTLS build step to your Emacs build for
> Windows, so the latest GnuTLS version can be used on that platform?  We
> had a long conversation about this and at least for now it seems to be
> the best approach (and we agreed it would not be a task for the core
> Emacs developers).  If you prefer, I can set up a BuildBot to produce
> the GnuTLS DLLs for you.

 From what Eli said about his experience building GnuTLS on W32 this is 
something I'd rather not take on. My time is rather limited.

I am happy to build against whichever GnuTLS lib with binaries is 
available for W32 wherever. Whether that is on Eli's site or the 
official GnuTLS site.

I will also include a link to a location where to obtain the binaries in 
my release announcements from now on.

Regarding shipping Emacs with the GnuTLS binaries, I am generally not 
opposed to doing that. But what about jpeg, gif, tiff support? I agree 
with Juanma who IIRC said that we are providing an _Emacs binary 
distribution_. This whole model does not fit the expectations in the 
Windows world. In 2012, Windows users expect an "Emacs for Windows" with 
all (binary) batteries included, an installer/uninstaller, etc. We don't 
supply that and unless somebody steps up and does the work necessary we 
won't. Whether politically speaking we should is another question.

Right now I am building against Eli's library v3.0.9. If you provide a 
more recent, working, binary build for Windows and there is a somewhat 
convenient way for me to get it (I can script downloading and unzip'ing) 
I can include it in the binary distribution. That is, of course, if 
nobody has compelling arguments why I should not.

Do we have to provide the source for GnuTLS if we include it in the 
distro or is it enough for it to be available on the GnuTLS site?

Christoph



  parent reply	other threads:[~2012-01-29 16:00 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
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 [this message]
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=4F256D1E.4070902@gmail.com \
    --to=cschol2112@googlemail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=lekktu@gmail.com \
    --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).