Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/3] RPM bug fixes...
Date: Wed, 17 Jun 2015 12:04:39 -0500	[thread overview]
Message-ID: <1434560682-89221-1-git-send-email-mark.hatle@windriver.com> (raw)

This set fixes a few problems that I recently noticed with RPM5.

The first item is a pure bug fix, the second and third are either bugs or an 
enhancements depending on how you look at it.

To test the first bug, you will need to enable 'lua' in the rpm recipe's
PACKAGECONFIG.  You can then verify behavor by running:

rpm --eval "%{_defaultdocdir} %{lua:print 'after'}"

If 'after' appears BEFORE the defaultdocdir value, then the bug is not fixed.

For the second/third items, if you install the necessary runtime environment
to use rpmbuild, you can attempt to build various spec files that use the
updated variables and verify the usage was correct.  (Not all spec files use
__cc, __cxx, etc.. so you may have to hand craft them.)

Mark Hatle (3):
  rpm: Fix lua 'print' statement capture
  rpm: Rebrand rpm custom macro paths to be distro specific
  rpm: Generate per distribution and multilib macro files

 .../rpm/rpm/rpm-lua-fix-print.patch                | 104 +++++++++++++++++++++
 meta/recipes-devtools/rpm/rpm_5.4.14.bb            |  87 ++++++++++++++++-
 2 files changed, 188 insertions(+), 3 deletions(-)
 create mode 100644 meta/recipes-devtools/rpm/rpm/rpm-lua-fix-print.patch

-- 
1.9.3



             reply	other threads:[~2015-06-17 17:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-17 17:04 Mark Hatle [this message]
2015-06-17 17:04 ` [PATCH 1/3] rpm: Fix lua 'print' statement capture Mark Hatle
2015-06-17 17:04 ` [PATCH 2/3] rpm: Rebrand rpm custom macro paths to be distro specific Mark Hatle
2015-06-17 17:04 ` [PATCH 3/3] rpm: Generate per distribution and multilib macro files Mark Hatle
2015-06-23 14:57   ` Richard Purdie

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=1434560682-89221-1-git-send-email-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