From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/2] Two small fixes, pseudo and rpm
Date: Thu, 12 Apr 2012 16:21:21 -0500 [thread overview]
Message-ID: <cover.1334265557.git.mark.hatle@windriver.com> (raw)
pseudo was adding in an rpath, prevent that
rpm-native was not resolving dependencies that looked like possible
filename properly.
The following changes since commit 71e95c744eaa4dda1b3237db2e13f666f121c92b:
package_rpm.bbclass: Set tmppath for rpm to somewhere which won't conflict with the rootfs (2012-04-12 21:24:55 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib mhatle/fixes
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=mhatle/fixes
Mark Hatle (2):
pseudo: Tell pseudo to avoid specifying an RPATH
rpm: Ensure that we check both providename and filepaths
meta/recipes-devtools/pseudo/pseudo.inc | 8 ++--
meta/recipes-devtools/pseudo/pseudo_1.3.bb | 2 +-
meta/recipes-devtools/pseudo/pseudo_git.bb | 2 +-
meta/recipes-devtools/rpm/rpm/rpm-resolvedep.patch | 36 ++++++++++++++++++++
meta/recipes-devtools/rpm/rpm_5.4.0.bb | 3 +-
5 files changed, 44 insertions(+), 7 deletions(-)
create mode 100644 meta/recipes-devtools/rpm/rpm/rpm-resolvedep.patch
--
1.7.3.4
next reply other threads:[~2012-04-12 21:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-12 21:21 Mark Hatle [this message]
2012-04-12 21:21 ` [PATCH 1/2] pseudo: Tell pseudo to avoid specifying an RPATH Mark Hatle
2012-04-13 15:13 ` Saul Wold
2012-04-13 15:22 ` Mark Hatle
2012-04-13 15:33 ` Richard Purdie
2012-04-13 15:40 ` Mark Hatle
2012-04-13 15:50 ` Richard Purdie
2012-04-12 21:21 ` [PATCH 2/2] rpm: Ensure that we check both providename and filepaths Mark Hatle
2012-04-12 21:19 ` Steve Sakoman
2012-04-13 15:11 ` [PATCH 0/2] Two small fixes, pseudo and rpm Saul Wold
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=cover.1334265557.git.mark.hatle@windriver.com \
--to=mark.hatle@windriver.com \
--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