From: Tomi Ollila <tomi.ollila@iki.fi>
To: Thomas Jost <schnouki@schnouki.net>
Cc: notmuch@notmuchmail.org
Subject: Re: [PATCH] Add pseudo-compatibility with gmime 2.6
Date: Fri, 20 Jan 2012 15:32:41 +0200 [thread overview]
Message-ID: <yf68vl2a492.fsf@taco2.nixu.fi> (raw)
In-Reply-To: <87k44n2qsw.fsf@schnouki.net>
On Fri, 20 Jan 2012 00:52:47 +0100, Thomas Jost <schnouki@schnouki.net> wrote:
>
> Here is how I did:
>
> (ldd notmuch | grep -q gmime-2.6) && test_subtest_known_broken
>
> ldd notmuch will show "/path/to/libgmime-2.4.so.*" or
> "libgmime-2.6.so.*" so we can easily check this in the test suite.
> It's a little hacky but it seems to work. AFAIK ldd is a pretty standard
> tool so it should be available (almost) everywhere. However if you have
> a better idea I'll be glad to hear it.
The "hack" is good in a sense that if that check fails in any case
the test_subtest_known_broken is not executed and we get FAIL instead of
BROKEN.
The subshell is unneeded:
ldd notmuch | grep -q gmime-2.6 && test_subtest_known_broken
does the trick (potentially less forks)... ok now I have to test ;)
haha:
$ rm xfoo.* xbar.*
$ strace -ff -o xfoo sh -c '(ldd /bin/ls | grep -q libc) && echo foo'
foo
$ ls xfoo.*
xfoo.14277 xfoo.14279 xfoo.14281 xfoo.14283 xfoo.14285
xfoo.14278 xfoo.14280 xfoo.14282 xfoo.14284
$ strace -ff -o xbar sh -c 'ldd /bin/ls | grep -q libc && echo foo'
foo
$ ls xbar.*
xbar.14292 xbar.14294 xbar.14296 xbar.14298
xbar.14293 xbar.14295 xbar.14297 xbar.14299
Tomi
next prev parent reply other threads:[~2012-01-20 13:32 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8762gbtd6p.fsf@schnouki.net>
2012-01-16 23:56 ` [PATCH] Add pseudo-compatibility with gmime 2.6 Thomas Jost
2012-01-17 0:43 ` Tim Stoakes
2012-01-17 1:08 ` Kazuo Teramoto
2012-01-17 3:47 ` Austin Clements
2012-01-17 10:48 ` Adrian Perez
2012-01-17 10:48 ` Thomas Jost
2012-01-17 10:50 ` [PATCH v2 1/2] show: don't use hex literals in JSON output Thomas Jost
2012-01-17 10:50 ` [PATCH v2 2/2] Add pseudo-compatibility with gmime 2.6 Thomas Jost
2012-01-17 12:48 ` Tomi Ollila
2012-01-17 13:23 ` Thomas Jost
2012-01-17 22:25 ` Austin Clements
2012-01-18 8:15 ` Tomi Ollila
2012-01-18 17:35 ` Austin Clements
2012-01-19 23:33 ` Thomas Jost
2012-01-19 23:32 ` Thomas Jost
2012-01-20 0:06 ` [PATCH v3 0/2] gmime 2.6 compatibilty, 3rd iteration Thomas Jost
2012-01-20 0:06 ` [PATCH v3 1/2] show: don't use hex literals in JSON output Thomas Jost
2012-01-20 0:06 ` [PATCH v3 2/2] Add compatibility with gmime 2.6 Thomas Jost
2012-01-20 4:10 ` Austin Clements
2012-01-20 9:37 ` Thomas Jost
2012-01-20 9:39 ` [PATCH v4 1/3] show: don't use hex literals in JSON output Thomas Jost
2012-01-20 9:39 ` [PATCH v4 2/3] Add compatibility with gmime 2.6 Thomas Jost
2012-01-20 16:33 ` Austin Clements
2012-01-20 22:45 ` Tomi Ollila
2012-01-21 13:10 ` David Bremner
2012-01-20 9:39 ` [PATCH v4 3/3] Update NEWS and INSTALL about " Thomas Jost
2012-01-20 16:39 ` Austin Clements
2012-01-22 0:29 ` [PATCH] Fix NEWS " Thomas Jost
2012-01-22 12:55 ` David Bremner
2012-01-21 13:11 ` [PATCH v4 3/3] Update NEWS and INSTALL " David Bremner
2012-01-20 11:55 ` [PATCH v4 1/3] show: don't use hex literals in JSON output David Bremner
2012-01-20 12:33 ` Thomas Jost
2012-01-20 13:20 ` David Bremner
2012-01-22 0:20 ` [PATCH] " Thomas Jost
2012-01-22 12:56 ` David Bremner
2012-01-18 17:19 ` [PATCH v2 2/2] Add pseudo-compatibility with gmime 2.6 Tom Prince
2012-01-18 18:00 ` Tomi Ollila
2012-01-19 23:47 ` Thomas Jost
2012-01-17 20:38 ` [PATCH] " Austin Clements
2012-01-19 23:52 ` Thomas Jost
2012-01-20 13:32 ` Tomi Ollila [this message]
2012-01-17 10:19 ` Adrian Perez
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=yf68vl2a492.fsf@taco2.nixu.fi \
--to=tomi.ollila@iki.fi \
--cc=notmuch@notmuchmail.org \
--cc=schnouki@schnouki.net \
/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).