From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: emacs-devel@gnu.org
Subject: Re: GnuTLS/TLS proposals for after the release
Date: Sat, 23 Jul 2016 10:56:27 +0300 [thread overview]
Message-ID: <83a8h8wzx0.fsf@gnu.org> (raw)
In-Reply-To: <bf42c51b-534e-c411-922a-192acdd2d281@cs.ucla.edu> (message from Paul Eggert on Sat, 23 Jul 2016 09:44:28 +0200)
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Sat, 23 Jul 2016 09:44:28 +0200
>
> On 07/22/2016 05:23 PM, Eli Zaretskii wrote:
> > I'd like to hear from more people who know about those platforms.
> > Paul, for example.
>
> I regularly build Emacs on old Solaris systems that lack libraries that
> we require for typical builds (e.g., libgif). I haven't checked whether
> these systems also lack libgnutls, and don't much care whether they do.
> If they lack it, I'll configure --with-gnutls=no; if not, not. So I'm in
> favor of the change that I proposed. Emacs will still need to work even
> if libgnutls is absent, so I'm not sure what practical effect this will
> have on Emacs development in the short run. But it should encourage more
> packagers to make sure Emacs is linked with libgnutls.
Thanks. This matches my thinking. So I don't object to the proposed
change (on master, of course; and please mention that in NEWS).
next prev parent reply other threads:[~2016-07-23 7:56 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-05 21:26 GnuTLS/TLS proposals for after the release Ted Zlatanov
2016-07-06 0:32 ` John Wiegley
2016-07-06 12:21 ` Ted Zlatanov
2016-07-06 14:25 ` Ted Zlatanov
2016-07-06 17:44 ` John Wiegley
2016-07-07 8:10 ` Robert Pluim
2016-07-12 13:52 ` Ted Zlatanov
2016-07-12 22:03 ` John Wiegley
2016-07-13 14:26 ` Eli Zaretskii
2016-07-13 14:43 ` Ted Zlatanov
2016-07-20 12:04 ` Lars Ingebrigtsen
2016-07-20 12:52 ` Stefan Monnier
2016-07-20 13:00 ` Compressing ELPA (was: GnuTLS/TLS proposals for after the release) Stefan Monnier
2016-08-02 20:58 ` Compressing ELPA John Wiegley
2016-08-02 22:04 ` Rostislav Svoboda
2016-08-02 22:25 ` Robert Weiner
2016-08-03 16:08 ` Clément Pit--Claudel
2016-08-03 16:29 ` Stefan Monnier
2016-07-20 13:14 ` GnuTLS/TLS proposals for after the release Ted Zlatanov
2016-07-20 14:21 ` Paul Eggert
2016-07-25 12:48 ` Ted Zlatanov
2016-07-25 13:01 ` Ted Zlatanov
2016-07-21 14:52 ` Eli Zaretskii
2016-07-21 15:22 ` Ted Zlatanov
2016-07-21 16:00 ` Eli Zaretskii
2016-07-21 16:35 ` Ted Zlatanov
2016-07-21 17:25 ` Lars Ingebrigtsen
2016-07-21 18:46 ` Eli Zaretskii
2016-07-22 14:38 ` Ted Zlatanov
2016-07-22 15:23 ` Eli Zaretskii
2016-07-23 7:44 ` Paul Eggert
2016-07-23 7:56 ` Eli Zaretskii [this message]
2016-07-22 14:38 ` Stefan Monnier
2016-07-22 15:22 ` Eli Zaretskii
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=83a8h8wzx0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=eggert@cs.ucla.edu \
--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).