From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] Update rpm
Date: Mon, 21 Dec 2009 10:14:26 +0100 [thread overview]
Message-ID: <87ljgwzo25.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <4e1837c9c17e549a134a69f9bf8829797d879bb4.1261380062.git.nkukard@lbsd.net> (Nigel Kukard's message of "Mon, 21 Dec 2009 07:21:05 +0000")
>>>>> "Nigel" == Nigel Kukard <nkukard@lbsd.net> writes:
Nigel> Signed-off-by: Nigel Kukard <nkukard@lbsd.net>
Nigel> ---
Nigel> package/rpm/Config.in | 26 ++-
Nigel> package/rpm/rpm-5.1.6_exclude-some-tools.patch | 12 -
Nigel> package/rpm/rpm-5.1.6_magic-file-fix.patch | 40 ----
Nigel> package/rpm/rpm-5.2.0_depends-fix.patch | 19 ++
Nigel> package/rpm/rpm-5.2.0_exclude-some-tools.patch | 30 +++
Nigel> package/rpm/rpm-5.2.0_no-parentdirs.patch | 14 ++
Nigel> package/rpm/rpm-5.2.0_ordering-fix.patch | 45 ++++
Nigel> package/rpm/rpm-5.2.0_parentdir-vs-requires.patch | 37 ++++
Nigel> package/rpm/rpm-5.2.0_short-circuit-c99.patch | 235 +++++++++++++++++++++
Nigel> package/rpm/rpm.mk | 21 ++-
Nigel> 10 files changed, 416 insertions(+), 63 deletions(-)
Nigel> delete mode 100755 package/rpm/rpm-5.1.6_exclude-some-tools.patch
Nigel> delete mode 100755 package/rpm/rpm-5.1.6_magic-file-fix.patch
Nigel> create mode 100644 package/rpm/rpm-5.2.0_depends-fix.patch
Nigel> create mode 100644 package/rpm/rpm-5.2.0_exclude-some-tools.patch
Nigel> create mode 100644 package/rpm/rpm-5.2.0_no-parentdirs.patch
Nigel> create mode 100644 package/rpm/rpm-5.2.0_ordering-fix.patch
Nigel> create mode 100644 package/rpm/rpm-5.2.0_parentdir-vs-requires.patch
Nigel> create mode 100644 package/rpm/rpm-5.2.0_short-circuit-c99.patch
Where does those patches come from? Are you the author? Have they been
pushed upstream where possible?
Nigel> diff --git a/package/rpm/Config.in b/package/rpm/Config.in
Nigel> index f4f7f90..d50a642 100644
Nigel> --- a/package/rpm/Config.in
Nigel> +++ b/package/rpm/Config.in
Nigel> @@ -1,14 +1,32 @@
Nigel> config BR2_PACKAGE_RPM
Nigel> bool "rpm"
Nigel> - select BR2_PACKAGE_ZLIB
Nigel> - select BR2_PACKAGE_BZIP2
Nigel> select BR2_PACKAGE_BEECRYPT
Nigel> select BR2_PACKAGE_POPT
Nigel> select BR2_PACKAGE_NEON
Nigel> select BR2_PACKAGE_NEON_ZLIB
Nigel> - select BR2_PACKAGE_NEON_EXPAT if BR2_PACKAGE_EXPAT
Nigel> - select BR2_PACKAGE_NEON_LIBXML2 if BR2_PACKAGE_LIBXML2
Nigel> + select BR2_PACKAGE_NEON_EXPAT if BR2_PACKAGE_EXPAT
Nigel> + select BR2_PACKAGE_NEON_LIBXML2 if BR2_PACKAGE_LIBXML2
Nigel> + select BR2_PACKAGE_NEON_SSL
Select doesn't work recursively, so you need to select openssl as well.
Nigel> help
Nigel> The RPM package management system.
Nigel> http://rpm5.org
Nigel> +
Nigel> +config BR2_PACKAGE_RPM_BZIP2_PAYLOADS
Nigel> + bool "support for bzip2 payloads"
Nigel> + depends on BR2_PACKAGE_RPM
Nigel> + select BR2_PACKAGE_BZIP2
Nigel> + help
Nigel> + Support for bzip2 payloads in RPM.
Nigel> +
Nigel> +config BR2_PACKAGE_RPM_XZ_PAYLOADS
Nigel> + bool "support for xz payloads"
Nigel> + depends on BR2_PACKAGE_RPM
Nigel> + depends on BR2_GCC_CROSS_CXX
Doesn't this need liblzma?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2009-12-21 9:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-21 7:21 [Buildroot] [pull request] Pull request for branch rpm-update Nigel Kukard
2009-12-21 7:21 ` [Buildroot] [PATCH 1/1] Update rpm Nigel Kukard
2009-12-21 9:14 ` Peter Korsgaard [this message]
2009-12-21 9:51 ` Nigel Kukard
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=87ljgwzo25.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.net \
/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