From: peder@news.klingenberg.no (Peder O. Klingenberg)
To: emacs-devel@gnu.org
Subject: Re: proposal: require GnuTLS 3.1.x (previous stable)
Date: Wed, 26 Nov 2014 15:12:44 +0100 [thread overview]
Message-ID: <ksr3wq6of7.fsf@netfonds.no> (raw)
In-Reply-To: 87mw7eaz2w.fsf@lifelogs.com
On Wed, Nov 26 2014 at 08:08, Ted Zlatanov wrote:
> Peder, your whole argument could have applied to supporting GnuTLS 1.x
> back when we added support for 2.x the first time, because people still
> used it and didn't want to upgrade their system. Inertia is not a bad
> thing, but we're talking about the master branch of The Most Advanced
> Editor Ever Invented(TM). Sacrifices must be made :)
I'm not arguing against requiring a newer GnuTLS. Far from it. I have
no deep opinions on the subject. Please don't read any such resistance
into anything I wrote.
Ivan asked why anyone would build master on an old system. I merely
offered my rationalisations for doing so.
> 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?
No need to argue with me, at least. The maintenance burden for
supporting older libraries is obvious. A cutover date of "tomorrow"
would be fine by me.
For my part, I'm fairly confident that I'll be able to aquire the
required version of GnuTLS, should my distribution not supply it. That
is a burden I accept by running my system as I do. If it turns out I'm
wrong, and compiling GnuTLS causes problems, then that will be a reason
to upgrade my distribution.
...Peder...
--
I wish a new life awaited _me_ in some off-world colony.
next prev parent reply other threads:[~2014-11-26 14:12 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 [this message]
2014-11-26 15:42 ` Stefan Monnier
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=ksr3wq6of7.fsf@netfonds.no \
--to=peder@news.klingenberg.no \
--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).