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: Using gnutls.c by default
Date: Thu, 05 May 2011 09:36:50 -0500	[thread overview]
Message-ID: <874o59z01p.fsf@lifelogs.com> (raw)
In-Reply-To: pkny62l5j1v.fsf@this.is.really.invalid

On Thu, 05 May 2011 16:16:44 +0200 Robert Pluim <rpluim@gmail.com> wrote: 

RP> Ted Zlatanov <tzz@lifelogs.com> writes:
>> On Thu, 5 May 2011 13:57:48 +0200 Juanma Barranquero <lekktu@gmail.com> wrote: 
>> 
JB> On Thu, May 5, 2011 at 13:50, Andy Moreton <andrewjmoreton@gmail.com> wrote:
>>>> It would be better to wait a week or two until there has been some
>>>> feedback about use of GnuTLS on Win32.
>> 
JB> We're talking about the trunk. Supporting GnuTLS by default is what
JB> will give us feedback, at least on Windows, where (much) fewer people
JB> is expected to build their own Emacs.
>> 
>> So far it's 5 to 1 votes in favor; I think it's badly needed on W32
>> where there are serious problems with the alternatives to GnuTLS.
>> 
>> Note that the user still has to (require 'gnutls) to use it.  We're just
>> adding the library support to Emacs.  Without (require 'gnutls)
>> `open-network-stream' won't use `gnutls-negotiate'.

RP> Oh, I thought Lars was proposing to go further than that, and always use
RP> GnuTLS if available. Makes no difference to my opinion, GnuTLS works for
RP> me :)

After re-reading the thread, you're right.  Sorry for the confusion, I
thought it was just about adding the library support.

So this proposal is to enable GnuTLS support for all the builds,
including W32, and then to make (require 'gnutls) unnecessary because it
will be done by `open-network-stream' by default.  The user has to
explicitly turn off gnutls.el support in order to get the old behavior.

Ted




  reply	other threads:[~2011-05-05 14:36 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-02 13:54 Using gnutls.c by default Lars Magne Ingebrigtsen
2011-05-02 17:57 ` Ted Zlatanov
2011-05-02 18:11   ` Lars Magne Ingebrigtsen
2011-05-02 19:06     ` Ted Zlatanov
2011-05-02 22:50   ` Christoph Scholtes
2011-05-02 23:09     ` Juanma Barranquero
2011-05-05 10:42       ` Ted Zlatanov
2011-05-05 11:27         ` Juanma Barranquero
2011-05-05 11:50         ` Andy Moreton
2011-05-05 11:57           ` Juanma Barranquero
2011-05-05 14:00             ` Ted Zlatanov
2011-05-05 14:16               ` Robert Pluim
2011-05-05 14:36                 ` Ted Zlatanov [this message]
2011-05-07 15:05                   ` T.V. Raman
2011-05-08  0:03                     ` Ted Zlatanov
2011-05-08  2:00                     ` Stefan Monnier
2011-05-05 12:10         ` Christoph Scholtes
2011-05-05 12:15           ` Juanma Barranquero
2011-05-05 12:17             ` Christoph Scholtes
2011-05-05 13:22         ` Robert Pluim

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=874o59z01p.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).