From: Saul Wold <sgw@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/5] Add rpm4 recipe and enable smartpm for rpm4
Date: Tue, 30 Sep 2014 10:16:50 -0700 [thread overview]
Message-ID: <cover.1412095567.git.sgw@linux.intel.com> (raw)
This patch series is the last bit to enable rpm4 base code. To use
this version you must set Preferred Version as such:
EFERRED_VERSION_rpm = "4.11.2"
PREFERRED_VERSION_rpm-native = "4.11.2"
The rootfs_rpm is a Work In Progress and I expect will not be accepted.
Sau!
The following changes since commit bff185f6252751a97dcdf7ddfe86b808a714fdc5:
dev-manual: Added a note to the EXTERNALSRC example about the class (2014-09-22 13:04:44 +0100)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib sgw/rpm4
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=sgw/rpm4
Saul Wold (5):
nss: nss.pc is not target specific
rpm5: add python-rpm PROVIDES
python-smartpm: Add patches for rpm4
rpm: add version 4.11.2
rootfs_rpm: remove hard depends on rpmresolve - WIP
meta/classes/rootfs_rpm.bbclass | 1 -
.../python/python-smartpm/smart-dflags.patch | 53 +--
.../python/python-smartpm/smart-rpm4-fixes.patch | 49 +++
.../python/python-smartpm_1.4.1.bb | 5 +-
.../add_RPMSENSE_MISSINGOK_to_rpmmodule.patch | 20 ++
.../rpm/rpm-4.11.2/disable_shortcircuited.patch | 23 ++
.../rpm/rpm-4.11.2/fix_libdir.patch | 19 +
meta/recipes-devtools/rpm/rpm-4.11.2/pythondeps.sh | 16 +
.../rpm/rpm-4.11.2/remove-db3-from-configure.patch | 26 ++
.../rpm/rpm-4.11.2/remove-dir-check.patch | 23 ++
.../rpm/rpm-4.11.2/rpm-scriptetexechelp.patch | 194 +++++++++++
.../rpm/rpm-4.11.2/support-suggests-tag.patch | 384 +++++++++++++++++++++
.../rpm/rpm-4.11.2/use-pkgconfig-for-python.patch | 38 ++
meta/recipes-devtools/rpm/rpm_4.11.2.bb | 133 +++++++
meta/recipes-devtools/rpm/rpm_5.4.14.bb | 1 +
meta/recipes-support/nss/nss.inc | 6 +-
16 files changed, 962 insertions(+), 29 deletions(-)
create mode 100644 meta/recipes-devtools/python/python-smartpm/smart-rpm4-fixes.patch
create mode 100644 meta/recipes-devtools/rpm/rpm-4.11.2/add_RPMSENSE_MISSINGOK_to_rpmmodule.patch
create mode 100644 meta/recipes-devtools/rpm/rpm-4.11.2/disable_shortcircuited.patch
create mode 100644 meta/recipes-devtools/rpm/rpm-4.11.2/fix_libdir.patch
create mode 100755 meta/recipes-devtools/rpm/rpm-4.11.2/pythondeps.sh
create mode 100644 meta/recipes-devtools/rpm/rpm-4.11.2/remove-db3-from-configure.patch
create mode 100644 meta/recipes-devtools/rpm/rpm-4.11.2/remove-dir-check.patch
create mode 100644 meta/recipes-devtools/rpm/rpm-4.11.2/rpm-scriptetexechelp.patch
create mode 100644 meta/recipes-devtools/rpm/rpm-4.11.2/support-suggests-tag.patch
create mode 100644 meta/recipes-devtools/rpm/rpm-4.11.2/use-pkgconfig-for-python.patch
create mode 100644 meta/recipes-devtools/rpm/rpm_4.11.2.bb
--
1.8.3.1
next reply other threads:[~2014-09-30 17:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-30 17:16 Saul Wold [this message]
2014-09-30 17:16 ` [PATCH 1/5] nss: nss.pc is not target specific Saul Wold
2014-09-30 17:16 ` [PATCH 2/5] rpm5: add python-rpm PROVIDES Saul Wold
2014-09-30 17:16 ` [PATCH 3/5] python-smartpm: Add patches for rpm4 Saul Wold
2014-09-30 17:16 ` [PATCH 4/5] rpm: add version 4.11.2 Saul Wold
2014-09-30 17:16 ` [PATCH 5/5] rootfs_rpm: remove hard depends on rpmresolve - WIP 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.1412095567.git.sgw@linux.intel.com \
--to=sgw@linux.intel.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