From: Joshua Lock <joshua.g.lock@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [RFC PATCH 0/3] Remove RPM 4
Date: Fri, 11 Mar 2016 14:07:28 +0000 [thread overview]
Message-ID: <cover.1457705106.git.joshua.g.lock@intel.com> (raw)
This series removes RPM 4 and code to support it from OE Core. There are
several known issues with using RPM 4 and it seems better to acknowledge it's
unsupported by removing it from OE-Core than to leave it in a non-functional
state.
Please review the following changes for suitability for inclusion. If you have
any objections or suggestions for improvement, please respond to the patches. If
you agree with the changes, please provide your Acked-by.
Regards,
Joshua
The following changes since commit 00d3fd571a8d261d065b43f5cf3076a381843984:
siteinfo: Add ppc64le support. (2016-03-10 23:06:46 +0000)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib joshuagl/rmrpm
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=joshuagl/rmrpm
Joshua Lock (3):
rpm: remove RPM 4
smartpm: remove rpm4 patch
lib/package_manager: remove RPM4 support code
meta/lib/oe/package_manager.py | 94 ++---
.../smart-add-for-rpm-ignoresize-check.patch | 20 +-
.../python/python-smartpm/smart-rpm4-fixes.patch | 49 ---
meta/recipes-devtools/python/python-smartpm_git.bb | 1 -
.../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 | 132 -------
14 files changed, 47 insertions(+), 992 deletions(-)
delete mode 100644 meta/recipes-devtools/python/python-smartpm/smart-rpm4-fixes.patch
delete mode 100644 meta/recipes-devtools/rpm/rpm-4.11.2/add_RPMSENSE_MISSINGOK_to_rpmmodule.patch
delete mode 100644 meta/recipes-devtools/rpm/rpm-4.11.2/disable_shortcircuited.patch
delete mode 100644 meta/recipes-devtools/rpm/rpm-4.11.2/fix_libdir.patch
delete mode 100755 meta/recipes-devtools/rpm/rpm-4.11.2/pythondeps.sh
delete mode 100644 meta/recipes-devtools/rpm/rpm-4.11.2/remove-db3-from-configure.patch
delete mode 100644 meta/recipes-devtools/rpm/rpm-4.11.2/remove-dir-check.patch
delete mode 100644 meta/recipes-devtools/rpm/rpm-4.11.2/rpm-scriptetexechelp.patch
delete mode 100644 meta/recipes-devtools/rpm/rpm-4.11.2/support-suggests-tag.patch
delete mode 100644 meta/recipes-devtools/rpm/rpm-4.11.2/use-pkgconfig-for-python.patch
delete mode 100644 meta/recipes-devtools/rpm/rpm_4.11.2.bb
--
2.5.0
next reply other threads:[~2016-03-11 14:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 14:07 Joshua Lock [this message]
2016-03-11 14:07 ` [RFC PATCH 1/3] rpm: remove RPM 4 Joshua Lock
2016-03-11 14:07 ` [RFC PATCH 2/3] smartpm: remove rpm4 patch Joshua Lock
2016-03-11 14:07 ` [RFC PATCH 3/3] lib/package_manager: remove RPM4 support code Joshua Lock
2016-03-11 17:41 ` [RFC PATCH 0/3] Remove RPM 4 Richard Purdie
2016-03-14 14:40 ` Joshua G Lock
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.1457705106.git.joshua.g.lock@intel.com \
--to=joshua.g.lock@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