From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/5] Zypper removal
Date: Wed, 23 Jan 2013 12:10:09 +0000 [thread overview]
Message-ID: <cover.1358942978.git.paul.eggleton@linux.intel.com> (raw)
The following changes since commit ffab86f13cafb10d8d6273b6af8cd9a3c84eae20:
prserv: add LOCALCOUNT to AUTOINCs migration feature (2013-01-22 16:01:17 +0000)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib paule/zypper-remove
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/zypper-remove
Paul Eggleton (5):
zypper: remove
libzypp: remove
sat-solver: remove
classes/image-swab: remove zypper-related references
libcheck: fix HOMEPAGE
meta/classes/image-swab.bbclass | 3 -
.../arm-workaround-global-constructor.patch | 71 ---
meta/recipes-extended/libzypp/libzypp/close.patch | 32 --
.../libzypp/libzypp/config-release.patch | 23 -
meta/recipes-extended/libzypp/libzypp/cstdio.patch | 49 --
.../libzypp/fix_for_compile_wth_gcc-4.6.0.patch | 22 -
.../libzypp/libzypp/hardcode-lib-fix.patch | 22 -
.../libzypp/libzypp/libzypp-compatargs.patch | 54 ---
.../libzypp/libzypp/libzypp-oearch.patch | 500 --------------------
.../libzypp/libzypp/libzypp-rpm549.patch | 32 --
.../mips-workaround-gcc-tribool-error.patch | 24 -
meta/recipes-extended/libzypp/libzypp/no-doc.patch | 33 --
.../libzypp/libzypp/rpm5-no-rpmdbinit.patch | 27 --
meta/recipes-extended/libzypp/libzypp/rpm5.patch | 32 --
meta/recipes-extended/libzypp/libzypp_git.bb | 160 -------
...fopen.c-Forward-port-to-zlib-1.2.6-gzFile.patch | 57 ---
.../sat-solver/sat-solver/cmake.patch | 31 --
.../sat-solver/sat-solver/db5.patch | 26 -
.../sat-solver/fix_gcc-4.6.0_compile_issue.patch | 115 -----
.../sat-solver/sat-solver/futimes.patch | 32 --
.../sat-solver/sat-solver/sat-solver_core.patch | 127 -----
.../sat-solver/sat-solver_obsolete.patch | 22 -
.../sat-solver/sat-solver/sat-solver_rpm5.patch | 69 ---
meta/recipes-extended/sat-solver/sat-solver_git.bb | 67 ---
meta/recipes-extended/zypper/zypper/cmake.patch | 22 -
.../zypper/zypper/cmake_libxml2.patch | 28 --
.../zypper/dso_linking_change_build_fix.patch | 60 ---
.../recipes-extended/zypper/zypper/gcc-scope.patch | 20 -
.../recipes-extended/zypper/zypper/rpm5-flag.patch | 18 -
meta/recipes-extended/zypper/zypper/rpmatch.patch | 23 -
meta/recipes-extended/zypper/zypper_git.bb | 29 --
meta/recipes-support/libcheck/libcheck_0.9.9.bb | 2 +-
32 files changed, 1 insertion(+), 1831 deletions(-)
delete mode 100644 meta/recipes-extended/libzypp/libzypp/arm-workaround-global-constructor.patch
delete mode 100644 meta/recipes-extended/libzypp/libzypp/close.patch
delete mode 100644 meta/recipes-extended/libzypp/libzypp/config-release.patch
delete mode 100644 meta/recipes-extended/libzypp/libzypp/cstdio.patch
delete mode 100644 meta/recipes-extended/libzypp/libzypp/fix_for_compile_wth_gcc-4.6.0.patch
delete mode 100644 meta/recipes-extended/libzypp/libzypp/hardcode-lib-fix.patch
delete mode 100644 meta/recipes-extended/libzypp/libzypp/libzypp-compatargs.patch
delete mode 100644 meta/recipes-extended/libzypp/libzypp/libzypp-oearch.patch
delete mode 100644 meta/recipes-extended/libzypp/libzypp/libzypp-rpm549.patch
delete mode 100644 meta/recipes-extended/libzypp/libzypp/mips-workaround-gcc-tribool-error.patch
delete mode 100644 meta/recipes-extended/libzypp/libzypp/no-doc.patch
delete mode 100644 meta/recipes-extended/libzypp/libzypp/rpm5-no-rpmdbinit.patch
delete mode 100644 meta/recipes-extended/libzypp/libzypp/rpm5.patch
delete mode 100644 meta/recipes-extended/libzypp/libzypp_git.bb
delete mode 100644 meta/recipes-extended/sat-solver/sat-solver/0001-sat_xfopen.c-Forward-port-to-zlib-1.2.6-gzFile.patch
delete mode 100644 meta/recipes-extended/sat-solver/sat-solver/cmake.patch
delete mode 100644 meta/recipes-extended/sat-solver/sat-solver/db5.patch
delete mode 100644 meta/recipes-extended/sat-solver/sat-solver/fix_gcc-4.6.0_compile_issue.patch
delete mode 100644 meta/recipes-extended/sat-solver/sat-solver/futimes.patch
delete mode 100644 meta/recipes-extended/sat-solver/sat-solver/sat-solver_core.patch
delete mode 100644 meta/recipes-extended/sat-solver/sat-solver/sat-solver_obsolete.patch
delete mode 100644 meta/recipes-extended/sat-solver/sat-solver/sat-solver_rpm5.patch
delete mode 100644 meta/recipes-extended/sat-solver/sat-solver_git.bb
delete mode 100644 meta/recipes-extended/zypper/zypper/cmake.patch
delete mode 100644 meta/recipes-extended/zypper/zypper/cmake_libxml2.patch
delete mode 100644 meta/recipes-extended/zypper/zypper/dso_linking_change_build_fix.patch
delete mode 100644 meta/recipes-extended/zypper/zypper/gcc-scope.patch
delete mode 100644 meta/recipes-extended/zypper/zypper/rpm5-flag.patch
delete mode 100644 meta/recipes-extended/zypper/zypper/rpmatch.patch
delete mode 100644 meta/recipes-extended/zypper/zypper_git.bb
--
1.7.10.4
next reply other threads:[~2013-01-23 12:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 12:10 Paul Eggleton [this message]
2013-01-23 12:10 ` [PATCH 1/5] zypper: remove Paul Eggleton
2013-01-23 12:10 ` [PATCH 2/5] libzypp: remove Paul Eggleton
2013-01-23 12:10 ` [PATCH 3/5] sat-solver: remove Paul Eggleton
2013-01-23 12:10 ` [PATCH 4/5] classes/image-swab: remove zypper-related references Paul Eggleton
2013-01-23 12:10 ` [PATCH 5/5] libcheck: fix HOMEPAGE Paul Eggleton
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.1358942978.git.paul.eggleton@linux.intel.com \
--to=paul.eggleton@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