unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: tzz@lifelogs.com, 27708@debbugs.gnu.org
Subject: bug#27708: [PROPOSED] Simplify configuration of HAVE_GNUTLS3 etc.
Date: Sun, 16 Jul 2017 19:08:45 +0300	[thread overview]
Message-ID: <837ez8e54i.fsf@gnu.org> (raw)
In-Reply-To: <6277b486-12c8-8363-cd9f-a79b6bda9304@cs.ucla.edu> (message from Paul Eggert on Sun, 16 Jul 2017 08:18:57 -0700)

> Cc: tzz@lifelogs.com, 27708@debbugs.gnu.org
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Sun, 16 Jul 2017 08:18:57 -0700
> 
> Eli Zaretskii wrote:
> > if
> > we want to allow as many of these APIs to be useful on as many
> > platforms, we need to do more work on the code.
> 
> One possible step forward is to use each of the APIs starting when they became 
> available, as opposed to the current practice of using some of them only in 
> GnuTLS v3 or later (even though they were available earlier). I could adjust my 
> proposed patch to do that, if you like. Unlike my proposed patch, this would 
> change Emacs behavior (but only on older GnuTLS platforms).

Yes, that's what I meant, but I think this won't be useful unless we
also introduce some fallbacks into the code which uses those new
functions.  AFAICT, it is the case in some of the new APIs that almost
all of the GnuTLS functions they use are available even before v3.X,
but then just one function they call needs 3.2.X or 3.4.X.  This makes
the entire API useless (it returns nil), which is a pity, since I'm
guessing we could code some workaround or maybe provide partial
functionality instead.  Alas, I don't know enough about these
functions to code such fallbacks.





  reply	other threads:[~2017-07-16 16:08 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-15 16:14 bug#27708: [PROPOSED] Simplify configuration of HAVE_GNUTLS3 etc Paul Eggert
2017-07-15 16:33 ` Eli Zaretskii
2017-07-15 19:11   ` Ted Zlatanov
2017-07-15 19:22     ` Eli Zaretskii
2017-07-16  0:31       ` Paul Eggert
2017-07-16  2:36         ` Eli Zaretskii
2017-07-16 15:18           ` Paul Eggert
2017-07-16 16:08             ` Eli Zaretskii [this message]
2017-07-17 15:03               ` Ted Zlatanov
2017-07-26 21:04                 ` Ted Zlatanov
2017-07-26 23:23                   ` Paul Eggert
2017-07-27 21:11                     ` Ted Zlatanov
2017-08-03  2:50                       ` Paul Eggert
2017-08-03 16:06                         ` Glenn Morris
2017-08-03 20:20                           ` Ted Zlatanov
2017-08-03 20:31                             ` Paul Eggert
2017-08-03 20:45                               ` Ted Zlatanov
2017-08-03 21:32                             ` Glenn Morris
2017-08-04  1:41                               ` Paul Eggert
2017-08-04 13:32                                 ` 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

  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=837ez8e54i.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=27708@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    --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.
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).