user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Eric Wong <>
Subject: libgmime experiences? (was: [PATCH] doc: update HACKING and TODO ...)
Date: Sat, 21 Sep 2019 22:40:03 +0000	[thread overview]
Message-ID: <20190921224003.GA21832@dcvr> (raw)
In-Reply-To: <>

Eric Wong <> wrote:
> --- a/HACKING
> +++ b/HACKING
> @@ -40,7 +40,8 @@ the shiny new.
>  Avoid relying on compiled modules too much.  Even if it is Free,
>  compiled code makes packages more expensive to audit, build,
>  distribute and verify.  public-inbox itself will only be implemented
> -in scripting languages (currently Perl 5).
> +in scripting languages (currently Perl 5) and optional JIT-compiled C
> +(via Inline::C)

I'm considering adding libgmime support after the 1.2 release
and creating an Email::MIME/msg_iter-compatible wrapper based
on it.

I've never used gmime as a user or hacker...

Pure-Perl Email::MIME will remain supported, though new versions
of Email::MIME use Email::Address::XS so there's already a
C/XS component which increases installation overhead.

My thoughts on gmime so far:

One big reason gmime looks good to me is that it offers mmap and
pipe APIs, so it hopefully deals well with big messages and
won't bloat/fragment the heap.

Another is Email::Simple::Header::_header_to_list being at the
top of some profiles, and I'm not convinced I could make it

gmime's been through several incompatible API/ABI versions, but
it seems Debian can support at least 2.6 and 3.0.  FreeBSD has
2.2, 2.4, 2.6 and 3.0, even!

gmime upstream also provides a PORTING document which should come
in handy.

The MIME::Fast wrapper for libgmime exists on CPAN, but that
hasn't been updated in years and isn't in Debian.  Both 3.0 and
2.6 APIs could be supported in parallel using Inline::C, and
more can be added in the future.

notmuch uses gmime, as does a lot of desktop software.

My experience with mainstream "desktop software" hasn't been
good, as they tends to be less stable in both user/programming
interfaces, and also more complex and difficult to debug than
server-oriented software.

However, looking at the Debian changelogs, there's only been one
CVE (CVE-2010-0409) from nearly a decade ago.  Maybe all the
bugs are fixed, or nobody really abuses it.

In any case, if I go through with this, I'll be running lots of
mail and random junk through it to ensure it doesn't break

  reply	other threads:[~2019-09-21 22:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-21  0:06 [PATCH] doc: update HACKING and TODO with a few items Eric Wong
2019-09-21 22:40 ` Eric Wong [this message]
2019-11-16  2:50   ` libgmime experiences? (was: [PATCH] doc: update HACKING and TODO ...) Eric Wong

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:

  List information:

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

  git send-email \
    --in-reply-to=20190921224003.GA21832@dcvr \ \ \

* 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

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