Gnus development mailing list
 help / color / mirror / Atom feed
From: Julien Danjou <julien@danjou.info>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org, emacs-devel@gnu.org
Subject: Re: gnutls status
Date: Fri, 26 Nov 2010 13:51:09 +0100	[thread overview]
Message-ID: <sa3hbf4i6yq.fsf@cigue.easter-eggs.fr> (raw)
In-Reply-To: <87ipzkmgfn.fsf@lifelogs.com> (Ted Zlatanov's message of "Fri, 26 Nov 2010 06:13:00 -0600")

[-- Attachment #1: Type: text/plain, Size: 1977 bytes --]

On Fri, Nov 26 2010, Ted Zlatanov wrote:

> 2.10.x and above let us set a callback function, which would make all of
> the above easier and more convenient from ELisp-land.  The problem is
> that 2.10.x hasn't been widely adopted in Debian and thus won't work by
> default.

It's in experimental. It won't go in sid until squeeze is released,
which should be very soon now. So there's nothing to wait IMHO.
At the time Emacs 24 will be released, gnutls 2.10 would have been
since a very long in Debian. :)

> This is essentially why I haven't worked on the GnuTLS support in a bit:
> I don't know the best way forward.  If anyone can suggest a good way to
> do it, I'm all ears.  I also don't know about 2.10.x's status in the
> major distros and whether Emacs can require that version or higher
> specifically.

My opinion is go with 2.10.

Some distro do not update often packages if they're is no urgent need
to, anyhow. So you will just be pushing them a bit, which is not a bad
thing. :)

Gentoo, OpenBSD, FreeBSD already have it FWIW. And Debian in
experimental, so it will end up in Debian and Ubuntu in a couple of
month top[1].

This is the development model I used for the last years in various
project like the awesome window manager, often requiring recent version
of libraries it uses. I consider I don't have enough time to write
compatibility code for older library release, while smart people write
better interface for us to use.
The only downside is for people using old OS for whatever reason. But
they *will have* to upgrade other time anyhow, so why not doing sooner
than later? Since we're talking a user program (not a production Web
server), there's no big counter-argument to this, IMHO.

Of course, YMMV, as your amount of spare time to be used writing
compatibility code. ;)

[1]  Depends if squeeze is released soon, of course.

-- 
Julien Danjou
// ᐰ <julien@danjou.info>   http://julien.danjou.info

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2010-11-26 12:51 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 [this message]
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       ` gnutls status Ted Zlatanov
2011-03-01 21:52         ` 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=sa3hbf4i6yq.fsf@cigue.easter-eggs.fr \
    --to=julien@danjou.info \
    --cc=ding@gnus.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.
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).