Re: [python] set rpath in setup.cfg

diff --git a/b7/95184187f12365d01662bb23148987b07ac5e7 b/b7/95184187f12365d01662bb23148987b07ac5e7
new file mode 100644 (file)
index 0000000..774672a
--- /dev/null
+++ b/b7/95184187f12365d01662bb23148987b07ac5e7
@@ -0,0 +1,118 @@
+Return-Path: <thomas@schwinge.name>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+       by olra.theworths.org (Postfix) with ESMTP id 39FD6429E27\r
+       for <notmuch@notmuchmail.org>; Sun, 16 Oct 2011 13:05:15 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: 0\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=0 tagged_above=-999 required=5\r
+       tests=[RCVD_IN_DNSWL_NONE=-0.0001] autolearn=disabled\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+       by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+       with ESMTP id s8E+tdMgrKS9 for <notmuch@notmuchmail.org>;\r
+       Sun, 16 Oct 2011 13:05:14 -0700 (PDT)\r
+Received: from smtprelay04.ispgateway.de (smtprelay04.ispgateway.de\r
+       [80.67.31.27])\r
+       by olra.theworths.org (Postfix) with ESMTP id 31F74429E26\r
+       for <notmuch@notmuchmail.org>; Sun, 16 Oct 2011 13:05:14 -0700 (PDT)\r
+Received: from [87.180.87.168] (helo=stokes.schwinge.homeip.net)\r
+       by smtprelay04.ispgateway.de with esmtpa (Exim 4.68)\r
+       (envelope-from <thomas@schwinge.name>) id 1RFWx5-00045r-Ss\r
+       for notmuch@notmuchmail.org; Sun, 16 Oct 2011 22:04:56 +0200\r
+Received: (qmail 28747 invoked from network); 16 Oct 2011 20:04:24 -0000\r
+Received: from kepler.schwinge.homeip.net (192.168.111.7)\r
+       by stokes.schwinge.homeip.net with QMQP; 16 Oct 2011 20:04:24 -0000\r
+Received: (nullmailer pid 20495 invoked by uid 1000);\r
+       Sun, 16 Oct 2011 20:04:24 -0000\r
+From: Thomas Schwinge <thomas@schwinge.name>\r
+To: Jameson Graef Rollins <jrollins@finestructure.net>, dtk <dtk@gmx.de>,\r
+       Ali Polatel <polatel@gmail.com>\r
+Subject: Re: [python] set rpath in setup.cfg\r
+In-Reply-To: <87pqi1s8ln.fsf@servo.finestructure.net>\r
+References: <6d84224ab757d84968df4db3a7b00fcb@jadE-Hamburg.de>\r
+       <20111012153051.GE21615@hayalet>\r
+       <d8e00c1f9be7bf018677a2c868e95e6d@jadE-Hamburg.de>\r
+       <87pqi1s8ln.fsf@servo.finestructure.net>\r
+User-Agent: Notmuch/0.9-101-g81dad07 (http://notmuchmail.org) Emacs/23.3.1\r
+       (i486-pc-linux-gnu)\r
+Date: Sun, 16 Oct 2011 22:04:23 +0200\r
+Message-ID: <8739es3dq0.fsf@kepler.schwinge.homeip.net>\r
+MIME-Version: 1.0\r
+Content-Type: multipart/signed; boundary="=-=-=";\r
+       micalg=pgp-sha1; protocol="application/pgp-signature"\r
+X-Df-Sender: dGhvbWFzQHNjaHdpbmdlLm5hbWU=\r
+Cc: notmuch@notmuchmail.org\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+       <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Sun, 16 Oct 2011 20:05:15 -0000\r
+\r
+--=-=-=\r
+Content-Type: text/plain; charset=utf-8\r
+Content-Transfer-Encoding: quoted-printable\r
+\r
+Hi!\r
+\r
+On Wed, 12 Oct 2011 23:34:28 -0700, Jameson Graef Rollins <jrollins@finestr=\r
+ucture.net> wrote:\r
+> On Thu, 13 Oct 2011 08:12:03 +0200, dtk <dtk@gmx.de> wrote:\r
+> > in my experience, it tends to cause awkward side effects that are hard =\r
+to\r
+> > debug, the main problem being that it overrides all default paths and is\r
+> > hard to target at a single problematic application.\r
+>=20\r
+> I think it's fairly straightforward to prepend a library path to the ld\r
+> library path without overriding all defaults with something like this\r
+> (for bash):\r
+>=20\r
+> LD_LIBRARY_PATH=3D/new/ld/path:$LD_LIBRARY_PATH\r
+\r
+This is in fact not safe, and may cause subtle issues: if LD_LIBRARY_PATH\r
+is empty initally, it'll evaluate to:\r
+\r
+    LD_LIBRARY_PATH=3D/new/ld/path:\r
+\r
+Of this one, the last element is empty, and ld.so will thus look into the\r
+current directory for libc.so, for example.  Now you cd /tmp/ and enter\r
+ls...  :-)\r
+\r
+Or, as it once bit me, you're on a system with such an LD_LIBRARY_PATH\r
+set (without me knowing about it).  You do glibc development, and wonder\r
+why some commands begin acting strangely when you're in the glibc build\r
+directory...\r
+\r
+Thus:\r
+\r
+    LD_LIBRARY_PATH=3D/new/ld/path${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH}\r
+\r
+\r
+Gr=C3=BC=C3=9Fe,\r
+ Thomas\r
+\r
+--=-=-=\r
+Content-Type: application/pgp-signature\r
+\r
+-----BEGIN PGP SIGNATURE-----\r
+Version: GnuPG v1.4.11 (GNU/Linux)\r
+\r
+iQEcBAEBAgAGBQJOmzjHAAoJEGe3hdm9kOii3t4IANBLzwybLBSjeTVYdB8o0Rm7\r
+nB0xHBZCBclI5xFB6GjiETvg0NoKDQOGy8JKw6+eQkHyvFAwodFc9/q4i5SiBeR8\r
+H5TmatS+G4EAVy3MgJlVljZg+NlSejHvEb44D4WUMI+3N5OLRa11TqAI2CnFGBeU\r
+ww/nDFRHTs7rlk/3/cBqejyzEyV8NMAm+HM3/fEYZV4gbKWMe1xj4Jh9yTXhmazJ\r
+mopAJ5A5kxu1o1AdJU12VNzPA4kFMLFwcffuZ8nJ02ahtSlueCcjnpwug67GFcAF\r
+DGM2CsojvywOuTRbAH5ynyexGzb5iCU3C3gmRJFq2nM64vS94cH3Y9w3z9YAmP0=\r
+=qzyS\r
+-----END PGP SIGNATURE-----\r
+--=-=-=--\r