From: Tomi Ollila <tomi.ollila@iki.fi>
To: notmuch@notmuchmail.org
Cc: Tomi Ollila <tomi.ollila@iki.fi>
Subject: [PATCH 2b/2] configure: print info about required gmime 2.4 or 2.6 versions
Date: Wed, 21 Mar 2012 21:18:50 +0200 [thread overview]
Message-ID: <1332281811-24710-2b-git-send-email-tomi.ollila@iki.fi> (raw)
In-Reply-To: <1332281811-24710-1-git-send-email-tomi.ollila@iki.fi>
In case required gmime (2.4 or 2.6) version if not found print information
about both alternatives (and currently minimal 2.6 version that is needed).
---
This replaces id:"1332281811-24710-2-git-send-email-tomi.ollila@iki.fi"
(having itself id:"1332281811-24710-2b-git-send-email-tomi.ollila@iki.fi")
IMHO this is better and more robust that the other one. trailing space
in $GMIME_24_VERSION causes no problems (that could have been avoided
but the code looks slighty clearer this way.
configure | 14 +++++++++-----
1 files changed, 9 insertions(+), 5 deletions(-)
diff --git a/configure b/configure
index 393f859..ace465b 100755
--- a/configure
+++ b/configure
@@ -48,8 +48,13 @@ WITH_EMACS=1
WITH_BASH=1
WITH_ZSH=1
-GMIME_24_VERSION='gmime-2.4'
-GMIME_26_VERSION='gmime-2.6 >= 2.6.7'
+# Compatible GMime versions (with constraints).
+# If using GMime 2.6, we need to have a version >= 2.6.5 to avoid a
+# crypto bug. We need 2.6.7 for permissive "From " header handling.
+GMIME_24_VERSION_CTR=''
+GMIME_24_VERSION="gmime-2.4 $GMIME_24_VERSION_CTR"
+GMIME_26_VERSION_CTR='>= 2.6.7'
+GMIME_26_VERSION="gmime-2.6 $GMIME_26_VERSION_CTR"
WITH_GMIME_VERSIONS="$GMIME_26_VERSION;$GMIME_24_VERSION"
@@ -259,8 +264,6 @@ if [ ${have_xapian} = "0" ]; then
errors=$((errors + 1))
fi
-# If using GMime 2.6, we need to have a version >= 2.6.5 to avoid a
-# crypto bug. We need 2.6.7 for permissive "From " header handling.
printf "Checking for GMime development files... "
have_gmime=0
IFS=';'
@@ -402,7 +405,8 @@ EOF
echo " http://xapian.org/"
fi
if [ $have_gmime -eq 0 ]; then
- echo " GMime 2.4 library (including development files such as headers)"
+ echo " Either GMime 2.4 library" $GMIME_24_VERSION_CTR "or GMime 2.6 library" $GMIME_26_VERSION_CTR
+ echo " (including development files such as headers)"
echo " http://spruce.sourceforge.net/gmime/"
echo
fi
--
1.7.8.2
next prev parent reply other threads:[~2012-03-21 19:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-20 22:16 [PATCH 1/2] configure: add empty line after each missing component message Tomi Ollila
2012-03-20 22:16 ` [PATCH 2/2] configure: print info about required gmime 2.4 or 2.6 versions Tomi Ollila
2012-03-21 19:18 ` Tomi Ollila [this message]
2012-04-05 11:04 ` [PATCH] configure: change gmime version in help message to 2.6 David Bremner
2012-04-06 15:33 ` David Bremner
[not found] <id:"1332281811-24710-1-git-send-email-tomi.ollila@iki.fi">
2012-03-21 19:15 ` [PATCH 2b/2] configure: print info about required gmime 2.4 or 2.6 versions Tomi Ollila
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=1332281811-24710-2b-git-send-email-tomi.ollila@iki.fi \
--to=tomi.ollila@iki.fi \
--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).