all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: William F Hammond <gellmu@gmail.com>
Cc: 20078@debbugs.gnu.org
Subject: bug#20078: imap with openssl
Date: Thu, 12 Mar 2015 10:24:07 -0400	[thread overview]
Message-ID: <jwv1tku47zs.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <CAH_0fy7Hop6edS9gSCisGuHDuSYxDZZQ0kEPyMKNKnzQ5TQXbw@mail.gmail.com> (William F. Hammond's message of "Wed, 11 Mar 2015 11:47:03 -0700")

> There's discussion in those threads about whether 'anyone' still uses
> imap.el and its calls to external openssl.  It arises, for example, when
> using mail-sources with, say, nnmbox.

I consider imap.el's use of an external process to be a bug.

> My 'crisis' arose in a sun/solaris system where neither starttls nor gnutls
> is available.  It seems that starttls is now no longer maintained (for
> cause) and, in my case, gnutls is not easy to build from source because of
> recursive library dependencies.

Hmm... we're definitely moving in the direction of requiring libgnutls
when building Emacs.

> Would it make sense for emacs to incorporate gnutls?

No, there be dragons.

> That way one could be sure for a given build of emacs that it would
> work with gnutls.

That would just mean that you wouldn't be able to build Emacs without
first solving the "recursive library dependencies".

But yes, I encourage you to try and solve these gnutls build problems,


        Stefan





  parent reply	other threads:[~2015-03-12 14:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-11  2:31 bug#20078: imap with openssl William F Hammond
2015-03-11 17:33 ` Glenn Morris
2015-03-11 18:47   ` William F Hammond
2015-03-11 18:59     ` Glenn Morris
2015-03-12 14:24     ` Stefan Monnier [this message]
2015-12-26 20:48       ` Lars Ingebrigtsen
2015-12-26 21:46         ` William F Hammond
2015-12-26 21:53           ` Lars Ingebrigtsen

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=jwv1tku47zs.fsf-monnier+emacsbugs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=20078@debbugs.gnu.org \
    --cc=gellmu@gmail.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 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.