From: Tomi Ollila <tomi.ollila@iki.fi>
To: David Bremner <david@tethera.net>,
Daniel Kahn Gillmor <dkg@fifthhorseman.net>,
Jeffrey Stedfast <jestedfa@microsoft.com>,
"notmuch\@notmuchmail.org" <notmuch@notmuchmail.org>
Cc: notmuch@freelists.org
Subject: RE: Upcoming GMime 3.0 changes
Date: Tue, 09 May 2017 23:02:48 +0300 [thread overview]
Message-ID: <m28tm5u7br.fsf@guru.guru-group.fi> (raw)
In-Reply-To: <871srx27dn.fsf@tesseract.cs.unb.ca>
On Tue, May 09 2017, David Bremner wrote:
> Daniel Kahn Gillmor <dkg@fifthhorseman.net> writes:
>
>>
>> out of curiosity, why do you think we won't be able to drop gmime-2.6
>> for a few years? if it's due to the debian release cycle and wanting to
>> backport notmuch to stretch, i don't think i'd mind providing backports
>> of gmime 3.0 for that purpose.
>
> That was what I was thinking about (and other distros with similar
> release cycles). But even among our own developers I don't know we can
> just throw a switch and say "install gmime 3.0 before you git pull".
I personally can compile gmime 3.0 for this (EOL'd) scientific linux 6.2
machine where I am writing this email, provided it does not need c/c++11
features(*). If gmime-3.0 could be statically linked to notmuch binary then
we could even provide an option to have it bundled into notmuch when
compiled (like I've included zlib...).
> I guess the other point is even with backports, there is still the issue
> of security support for older releases. We'll need to maintain the 2.6
> stuff in a branch, even if it only gets security/severe bug updates.
But these go to releases (how many old of those) which still have support
for gmime 2.6...
>
> Another question is how long Jeff plans to support 2.6 with bug fixes.
>
> d
Tomi
(*) I compiled Xapian 1.4 for Fedora 25; compiled fine and notmuch worked
with it. On SL6.2 compilation failed, and when running
/opt/rh/devtoolset-2/root/usr/bin/gcc compilation crashed at some point,
prev parent reply other threads:[~2017-05-09 20:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-13 22:43 Upcoming GMime 3.0 changes Jeffrey Stedfast
2017-03-14 13:17 ` David Bremner
2017-03-14 18:03 ` Jeffrey Stedfast
2017-05-09 13:37 ` David Bremner
2017-05-09 17:02 ` Daniel Kahn Gillmor
2017-05-09 18:49 ` David Bremner
2017-05-09 20:02 ` Tomi Ollila [this message]
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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m28tm5u7br.fsf@guru.guru-group.fi \
--to=tomi.ollila@iki.fi \
--cc=david@tethera.net \
--cc=dkg@fifthhorseman.net \
--cc=jestedfa@microsoft.com \
--cc=notmuch@freelists.org \
--cc=notmuch@notmuchmail.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://yhetil.org/notmuch.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).