Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Cc: emacs-devel@gnu.org
Subject: Re: gnutls status
Date: Tue, 14 Dec 2010 16:59:34 -0600	[thread overview]
Message-ID: <87tyigm04p.fsf@lifelogs.com> (raw)
In-Reply-To: <m3bp5cdvkw.fsf@quimbies.gnus.org>

On Fri, 26 Nov 2010 15:10:39 +0100 Lars Magne Ingebrigtsen <larsi@gnus.org> wrote: 

LMI> Is 2.10.x at least backwards-compatible, so that if we do implement the
LMI> complicated 2.8.x features, it'll continue to work in the future, too?

Yes.  They try really hard to keep backwards compatibility.  I'd guess
for all 2.x releases we'll be OK unless there's newer features we simply
must have :)

>> I think every package should explicitly choose to support gnutls.el, it
>> shouldn't be an Emacs-wide choice.  There's too many configuration
>> options that depend on the purpose.  For instance IMAP and HTTPS have
>> really different security needs.

LMI> True.  On the other hand, look at `nnimap-open-connection' and weep.  It
LMI> started off as a simple function and grew into a monster.  That's why I
LMI> haven't adapted nntp/pop3/etc to use gnutls yet -- I don't want to have
LMI> to repeat the same code all over the place.

...thanks for working on proto-stream.el, it's made all this much simpler.

On Fri, 26 Nov 2010 13:51:09 +0100 Julien Danjou <julien@danjou.info> wrote: 

JD> My opinion is go with 2.10.

On Sat, 27 Nov 2010 09:28:11 -0500 Stefan Monnier <monnier@IRO.UMontreal.CA> wrote: 

>> So gnutls 2.10 will not be in Debian stable when Emacs 24 get released
>> (unless Emacs 24 is released after mid-2012). But most users won't try
>> to install Emacs 24 on it anyway.

SM> That's a good point.  Especially since gnutls is not indispensable for
SM> Emacs, so as long as we properly handle the case where the gnutls library
SM> to too old (either by not using it, or by using some fallback code),
SM> then I'm OK with it.

OK, I will put upgrading Emacs' support of GnuTLS to 2.10 on my TODO
list.  Which means it won't happen soon, so if anyone else is feeling
frisky, go ahead and do it.  I listed what's necessary in my original
e-mail here; basically it's callbacks but there's other features in the
2.10 API we should use if possible.

I think that supporting 2.8 is counterproductive so I'll happily target
only 2.10.  I think that's reasonable and doesn't put a big burden on
the users and distros.

Ted




  parent reply	other threads:[~2010-12-14 22:59 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-25 17:29 Julien Danjou
2010-11-26  0:28 ` Lars Magne Ingebrigtsen
2010-11-26 12:13   ` Ted Zlatanov
2010-11-26 12:51     ` Julien Danjou
2010-11-26 15:02       ` Stefan Monnier
2010-11-26 15:56         ` Julien Danjou
2010-11-26 18:42           ` Stefan Monnier
2010-11-27  9:36             ` Julien Danjou
2010-11-27 14:28               ` Stefan Monnier
2010-11-28  9:55               ` Lars Magne Ingebrigtsen
2010-11-26 14:10     ` Lars Magne Ingebrigtsen
2010-11-27 14:18       ` Lars Magne Ingebrigtsen
2010-11-27 14:40         ` Lars Magne Ingebrigtsen
2010-11-27 15:31           ` Lars Magne Ingebrigtsen
2010-11-27 16:04             ` Lars Magne Ingebrigtsen
2010-11-27 16:37               ` Steinar Bang
2010-11-27 16:41                 ` Lars Magne Ingebrigtsen
2010-11-27 16:59                   ` Lars Magne Ingebrigtsen
2010-11-27 17:33                     ` Dan Christensen
2010-11-27 17:36                       ` Lars Magne Ingebrigtsen
2010-11-27 17:42                         ` Lars Magne Ingebrigtsen
2010-11-28  2:36             ` Automatic STARTTLS upgrades (was: gnutls status) Lars Magne Ingebrigtsen
2010-11-28 12:28               ` Automatic STARTTLS upgrades Lars Magne Ingebrigtsen
2010-11-28 13:34                 ` Lars Magne Ingebrigtsen
2010-12-14 22:59       ` Ted Zlatanov [this message]
2011-03-01 21:52         ` gnutls status Ted Zlatanov
2011-03-05 11:01           ` Lars Magne Ingebrigtsen
2011-03-05 14:46             ` Ted Zlatanov

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87tyigm04p.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=ding@gnus.org \
    --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.
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 NNTP newsgroup(s).