From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id DB11D6DE0B64 for ; Tue, 9 May 2017 13:03:27 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: 0.496 X-Spam-Level: X-Spam-Status: No, score=0.496 tagged_above=-999 required=5 tests=[AWL=-0.156, SPF_NEUTRAL=0.652] autolearn=disabled Received: from arlo.cworth.org ([127.0.0.1]) by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uu9bY2O8MEo7 for ; Tue, 9 May 2017 13:03:26 -0700 (PDT) Received: from guru.guru-group.fi (guru.guru-group.fi [46.183.73.34]) by arlo.cworth.org (Postfix) with ESMTP id 91EF46DE091E for ; Tue, 9 May 2017 13:03:25 -0700 (PDT) Received: from guru.guru-group.fi (localhost [IPv6:::1]) by guru.guru-group.fi (Postfix) with ESMTP id CA6C110019F; Tue, 9 May 2017 23:02:48 +0300 (EEST) From: Tomi Ollila To: David Bremner , Daniel Kahn Gillmor , Jeffrey Stedfast , "notmuch\@notmuchmail.org" Cc: notmuch@freelists.org Subject: RE: Upcoming GMime 3.0 changes In-Reply-To: <871srx27dn.fsf@tesseract.cs.unb.ca> References: <87mvcom1z8.fsf@tethera.net> <87k25q178l.fsf@tesseract.cs.unb.ca> <87shkeklpi.fsf@fifthhorseman.net> <871srx27dn.fsf@tesseract.cs.unb.ca> User-Agent: Notmuch/0.24+52~g1f96813 (https://notmuchmail.org) Emacs/25.1.1 (x86_64-unknown-linux-gnu) X-Face: HhBM'cA~ MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 May 2017 20:03:28 -0000 On Tue, May 09 2017, David Bremner wrote: > Daniel Kahn Gillmor 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,