all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ivan Shmakov <ivan@siamics.net>
To: emacs-devel@gnu.org
Subject: Re: proposal: require GnuTLS 3.1.x (previous stable)
Date: Tue, 25 Nov 2014 18:55:34 +0000	[thread overview]
Message-ID: <87h9xnqfdl.fsf@violet.siamics.net> (raw)
In-Reply-To: <m3sih78e99.fsf@stories.gnus.org> (Lars Magne Ingebrigtsen's message of "Tue, 25 Nov 2014 16:57:06 +0100")

>>>>> Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
>>>>> Ted Zlatanov <tzz@lifelogs.com> writes:

 >> Conditionally supporting GnuTLS 2.6.6 is a pain because many
 >> functions were added since then.  It complicates the code
 >> significantly today and for the future, possibly hiding bugs in the
 >> compatibility layers.  We're already starting to see these
 >> compilation issues in the bug tracker and on emacs-devel and it
 >> would be nice to cut the cord now.

 > I think it'll be many years before there is a non-significant number
 > of gnutls 2.x users out there.  The current Debian Stable uses 2.12,

	Yet Jessie is already frozen, so I guess we may see Debian 8
	released in the first half (if not quarter) of 2015.

	Personally, I’d suggest retaining GnuTLS 2 support until a month
	or two after that at the least.

 > and the various LTS versions of the different GNU/Linux distributions
 > will remain on 2.x for a Long Time, I think.

	Yes, although I’d rather question the necessity of building
	Emacs ‘master’ on an LTS GNU/Linux system.  If the intent is to
	use the last decade’s versions of Libc and Coreutils, – why
	Emacs has to be newer than that?

	Especially given that the older versions of the system, when
	necessary to support legacy software, could be just as well be
	run in chroot(2) environments.  (Or even be entirely “virtual.”)

-- 
FSF associate member #7257  http://boycottsystemd.org/  … 3013 B6A0 230E 334A



  parent reply	other threads:[~2014-11-25 18:55 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 [this message]
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
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

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

  git send-email \
    --in-reply-to=87h9xnqfdl.fsf@violet.siamics.net \
    --to=ivan@siamics.net \
    --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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.