From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: emacs-devel@gnu.org
Subject: Re: proposal: require GnuTLS 3.1.x (previous stable)
Date: Wed, 26 Nov 2014 10:42:37 -0500 [thread overview]
Message-ID: <jwvtx1mhtab.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87mw7eaz2w.fsf@lifelogs.com> (Ted Zlatanov's message of "Wed, 26 Nov 2014 08:08:55 -0500")
> 1) support for 2.x requires a specific contortion in the code
AFAICT, there's no such contortions yet. The needed ifdefs are fairly
simple and clean.
> 1) both 2.x and 3.x are installed (yes, it happens)
> 2) the user inadvertently compiles with 2.x
> 3) the user gets bug/security hole surprise
That doesn't sound very likely either, so I'm not worried about that risk.
> I'm sure we can argue about this for a while, but I personally would
> just like to set a cutover date where GnuTLS 2.x is not supported, not
> debate convenience and featuritis. How about Emacs 26?
We usually consider it OK to drop support for things that are "older
than Debian stable" or thereabout. But usually it depends a lot on the
cost of maintaining this backward compatibility. In this case, the cost
seems to be very reasonable, so I see no reason to drop support for
GnuTLS2 at this stage. Those tradeoffs change over time, so by Emacs-26
it's quite likely that we'll get rid of GnuTLS2 support, indeed.
Stefan
next prev parent reply other threads:[~2014-11-26 15:42 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-23 18:38 Build failure (master; MS-Windows) Dani Moncayo
2014-11-23 21:41 ` Dani Moncayo
2014-11-23 22:07 ` Lars Magne Ingebrigtsen
2014-11-23 22:52 ` Dani Moncayo
2014-11-23 22:57 ` Lars Magne Ingebrigtsen
2014-11-23 23:09 ` Dani Moncayo
2014-11-25 9:32 ` proposal: require GnuTLS 3.1.x (previous stable) (was: Build failure (master; MS-Windows)) Ted Zlatanov
2014-11-25 15:57 ` proposal: require GnuTLS 3.1.x (previous stable) Lars Magne Ingebrigtsen
2014-11-25 16:28 ` Ted Zlatanov
2014-11-25 16:38 ` Buildbot for Emacs? (was: proposal: require GnuTLS 3.1.x (previous stable)) Lars Magne Ingebrigtsen
2014-11-25 16:50 ` Buildbot for Emacs? Glenn Morris
2014-11-25 16:55 ` Ted Zlatanov
2014-11-25 22:15 ` Glenn Morris
2014-11-25 23:12 ` Ted Zlatanov
2014-11-26 9:52 ` Tom
2014-11-25 17:05 ` Lars Magne Ingebrigtsen
2014-11-25 22:14 ` Glenn Morris
2014-11-25 17:34 ` proposal: require GnuTLS 3.1.x (previous stable) Stefan Monnier
2014-11-25 18:55 ` Ivan Shmakov
2014-11-26 9:14 ` Peder O. Klingenberg
2014-11-26 12:57 ` Ivan Shmakov
2014-11-26 13:47 ` Peder O. Klingenberg
2014-11-26 13:08 ` Ted Zlatanov
2014-11-26 14:12 ` Peder O. Klingenberg
2014-11-26 15:42 ` Stefan Monnier [this message]
2014-11-26 16:52 ` Ted Zlatanov
2014-11-26 21:18 ` Ted Zlatanov
2014-11-26 21:37 ` Lars Magne Ingebrigtsen
2014-11-27 2:13 ` Stefan Monnier
2014-11-27 2:33 ` Ted Zlatanov
2014-11-28 18:51 ` Ted Zlatanov
2014-11-28 19:31 ` Stefan Monnier
2014-11-29 20:02 ` Glenn Morris
2014-11-26 13:46 ` Michael Welsh Duggan
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=jwvtx1mhtab.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--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).