From: Kumar Gala <galak@kernel.crashing.org>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 3/4] telepathy-python: utilize python-dir to respect libdir/site-packages path
Date: Tue, 9 Aug 2011 13:36:31 -0500 [thread overview]
Message-ID: <1312914992-18260-4-git-send-email-galak@kernel.crashing.org> (raw)
In-Reply-To: <1312914992-18260-3-git-send-email-galak@kernel.crashing.org>
Fixes issue of libdir is set to something like '/usr/lib64'.
Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
---
.../telepathy/telepathy-python_0.15.19.bb | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-connectivity/telepathy/telepathy-python_0.15.19.bb b/meta/recipes-connectivity/telepathy/telepathy-python_0.15.19.bb
index ead8dea..fde4006 100644
--- a/meta/recipes-connectivity/telepathy/telepathy-python_0.15.19.bb
+++ b/meta/recipes-connectivity/telepathy/telepathy-python_0.15.19.bb
@@ -9,9 +9,9 @@ RDEPENDS_${PN} += "python-dbus"
SRC_URI = "http://telepathy.freedesktop.org/releases/${BPN}/${BPN}-${PV}.tar.gz \
file://parallel_make.patch"
-PR = "r2"
+PR = "r3"
-inherit autotools
+inherit autotools python-dir
SRC_URI[md5sum] = "f7ca25ab3c88874015b7e9728f7f3017"
SRC_URI[sha256sum] = "244c0e1bf4bbd78ae298ea659fe10bf3a73738db550156767cc2477aedf72376"
--
1.7.3.4
next prev parent reply other threads:[~2011-08-09 18:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-09 18:36 [PATCH 0/4] python libdir / site-packages path cleanup Kumar Gala
2011-08-09 18:36 ` [PATCH 1/4] python-dir: specify am_cv_python_pythondir & am_cv_python_pyexecdir Kumar Gala
2011-08-09 18:36 ` [PATCH 2/4] xcb-proto: use python-dir class for proper path setting Kumar Gala
2011-08-09 18:36 ` Kumar Gala [this message]
2011-08-09 18:36 ` [PATCH 4/4] gnome-doc-utils: respect python-dir setting EXTRA_OECONF Kumar Gala
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1312914992-18260-4-git-send-email-galak@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=openembedded-core@lists.openembedded.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox