From: David Bremner <david@tethera.net>
To: Daniel Lee Harple <dlh@harple.com>, notmuch@notmuchmail.org
Subject: Re: [PATCH] NEWS,
 python: add --libnotmuch-dir option to "setup.py install"
In-Reply-To:
 <CA+7LD1FBuvM8UM1WX-QgKg4haK_iy11MuFZpW3A6oTc8x+9roQ@mail.gmail.com>
References:
 <CA+7LD1FBuvM8UM1WX-QgKg4haK_iy11MuFZpW3A6oTc8x+9roQ@mail.gmail.com>
User-Agent: Notmuch/0.22.1~rc0 (http://notmuchmail.org) Emacs/24.5.1
 (x86_64-pc-linux-gnu)
Date: Fri, 01 Jul 2016 18:31:15 +0200
Message-ID: <87furtgw18.fsf@maritornes.cs.unb.ca>
MIME-Version: 1.0
Content-Type: text/plain
Precedence: list

Daniel Lee Harple <dlh@harple.com> writes:

> This change fixes the python bindings on OS X 10.11, which introduced a
> feature called System Integrity Protection. The /usr/bin/python
> executable has the "restricted" flag set, which means dlopen() requires
> an absolute path to the library that is to be loaded.

Thanks for the patch. I'll let Justus (in copy) decide what the best way
to deal with this issue is.

I just wanted to point both of you (as an example) to commit

  233b5528cd4

Which avoids re-computing the name of the shared library in the ruby
bindings build system since it is already computed by the notmuch
configure script. If possibly, I'd like to centralize these
computations, so that we don't have to litter the entire source with
various "if Darwin then blah" choices. And obviously it's better not to
have update many places every time MacOS changes it's mind.

I guess some people might like to build the bindings outside the notmuch
source tree (via pypi or whatever). That's not a case I personally want
to support, but I defer to Justus.

d