unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Subject: Re: GnuTLS updates proposal
Date: Sat, 25 May 2013 00:47:41 -0400	[thread overview]
Message-ID: <jwv1u8visav.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <878v3322ha.fsf@lifelogs.com> (Ted Zlatanov's message of "Fri, 24 May 2013 22:54:41 -0400")

SM> Now I lost you.  How did we go from "gnutls" to "we"?
SM> Shouldn't some gnutls guys take care of that?

> So far they have not and it's not a priority to them.  Eli did a lot of
> work cleaning up the code and getting it to compile--it's thanks to him
> that Emacs has a recent GnuTLS DLL.

So, why should this fall on us?  I mean, is Emacs the only program
using gnutls?
If so, why?  what do other programs use?
If not, what do the other programs do about it?

> So, as far as building the GnuTLS DLLs, I'm hopeful we'll find a way to
> automate that but not hopeful that it will happen on the GnuTLS
> maintainers' side.  Building them on Mac OS X is trivial.  This is the
> "hard work" part and Eli already pointed out we'll need volunteers and
> resources.

Ah, so the problem is not only for Windows but also for Mac OS X?

> Whoever provides the actual DLLs, there has to be a package maintainer
> for the GNU ELPA package of GnuTLS;

As a user, I wouldn't like it for a program such as Emacs to decide it
will take over responsibility for a generic library used by other
programs, so I find the idea of distributing it via GNU ELPA rather odd.


        Stefan



  reply	other threads:[~2013-05-25  4:47 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87k3mw79iv.fsf@lifelogs.com>
     [not found] ` <CALDnm51ZBQn_T0w43TfNiui+nfBcJL5z_4egAXmtwdHOW3qCXQ@mail.gmail.com>
2013-05-19  3:17   ` bug#14380: 24.3; `network-stream-open-tls' fails in some imap servers on w32 Ted Zlatanov
2013-05-19 11:45     ` João Távora
2013-05-19 23:05       ` Ted Zlatanov
2013-05-20  2:08         ` Juanma Barranquero
2013-05-20  9:58           ` Ted Zlatanov
2013-05-20 15:21             ` Juanma Barranquero
2013-05-24 19:32               ` Ted Zlatanov
2013-05-24 19:50                 ` Eli Zaretskii
2013-05-24 21:55                   ` Ted Zlatanov
2013-05-25  6:42                     ` Eli Zaretskii
2013-05-25 22:18                       ` Ted Zlatanov
2013-05-26  2:52                         ` Eli Zaretskii
2013-05-26 21:32                           ` Ted Zlatanov
2013-05-26 19:59                         ` Eli Zaretskii
2013-05-26 21:31                           ` Ted Zlatanov
2013-05-24 19:51                 ` Stefan Monnier
2013-05-24 21:53                   ` GnuTLS updates proposal (was: bug#14380: 24.3; `network-stream-open-tls' fails in some imap servers on w32) Ted Zlatanov
2013-05-25  1:52                     ` GnuTLS updates proposal Stefan Monnier
2013-05-25  2:54                       ` Ted Zlatanov
2013-05-25  4:47                         ` Stefan Monnier [this message]
2013-05-25  6:25                           ` Stephen J. Turnbull
2013-05-25 22:28                           ` Ted Zlatanov
2013-05-26  4:51                             ` Richard Stallman
2013-05-26 21:28                               ` Ted Zlatanov
2013-05-25  6:39                     ` GnuTLS updates proposal (was: bug#14380: 24.3; `network-stream-open-tls' fails in some imap servers on w32) Eli Zaretskii
2013-05-25  7:10                       ` GnuTLS updates proposal Stefan Monnier
2013-05-26 21:34                         ` Ted Zlatanov
2013-06-05 14:57                           ` Ted Zlatanov
2013-05-26  1:53                       ` GnuTLS updates proposal (was: bug#14380: 24.3; `network-stream-open-tls' fails in some imap servers on w32) Juanma Barranquero
2013-05-20 16:17             ` bug#14380: 24.3; `network-stream-open-tls' fails in some imap servers on w32 Eli Zaretskii
2013-05-24 19:27               ` Ted Zlatanov
2013-05-20 22:07         ` João Távora
2013-06-05 15:06           ` Ted Zlatanov
2013-06-06  8:15             ` João Távora

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=jwv1u8visav.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).