From: Phil Blundell <pb@pbcl.net>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 04/20] package_rpm.bbclass:Make the regexp less greedy
Date: Tue, 27 Aug 2013 19:47:56 +0100 [thread overview]
Message-ID: <1377629276.4083.101.camel@x121e.pbcl.net> (raw)
In-Reply-To: <621ba27fe578346e2feae489fba4d576148299fc.1377623208.git.raj.khem@gmail.com>
On Tue, 2013-08-27 at 10:15 -0700, Khem Raj wrote:
> This causes issues when postinstalls have ERROR keywords
> its interpreted as error and image build is cancelled
>
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
As I mentioned before, "the regexp" isn't a very satisfactory
description of the locus for this change, given that the file contains
many regexps. I'm also not entirely convinced that this patch really
makes the regexp "less greedy" in any meaningful way: it makes it less
prone to unintended matches, but that's a different issue to greediness.
p.
next prev parent reply other threads:[~2013-08-27 18:48 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-27 17:11 [PATCH V4 00/20] Add python 3 support Khem Raj
2013-08-27 17:15 ` [PATCH 01/20] generate-manifest-3.3.py: Add script to generate python 3.3 manifests Khem Raj
2013-08-27 17:15 ` [PATCH 02/20] python-3.3-manifest: Add python3 manifest file Khem Raj
2013-08-27 17:15 ` [PATCH 03/20] python3native.bbclass: Add python3 abstraction class Khem Raj
2013-08-27 17:15 ` [PATCH 04/20] package_rpm.bbclass:Make the regexp less greedy Khem Raj
2013-08-27 18:47 ` Phil Blundell [this message]
2013-08-28 6:15 ` Khem Raj
2013-08-27 17:15 ` [PATCH 05/20] classes/distutils: Introduce PYTHON_PN Khem Raj
2013-08-27 17:15 ` [PATCH 06/20] classes: Add distutils for python3 Khem Raj
2013-08-27 17:15 ` [PATCH 07/20] distutils: Introduce PYTHON_ABI variable Khem Raj
2013-08-27 17:15 ` [PATCH 08/20] distutils3: Do build_ext as separate step during compile Khem Raj
2013-08-27 17:15 ` [PATCH 09/20] python3: Add recipes Khem Raj
2013-08-27 17:15 ` [PATCH 10/20] python3: Add native recipe Khem Raj
2013-08-27 17:15 ` [PATCH 11/20] python_2.7.3.bb: Inherit python-dir Khem Raj
2013-08-27 17:15 ` [PATCH 12/20] python-distribute: Add recipes for python2 and python3 Khem Raj
2013-08-27 17:15 ` [PATCH 13/20] python3: Upgrade to 3.3.2 Khem Raj
2013-08-27 17:15 ` [PATCH 14/20] distutils3.bbclass: Fix typo and use proper values for target sysroot Khem Raj
2013-08-27 17:15 ` [PATCH 15/20] python3, python3-native: Consider OE staging installation Khem Raj
2013-08-27 17:15 ` [PATCH 16/20] python3: Fix host include contamination issue Khem Raj
2013-08-27 17:15 ` [PATCH 17/20] distutils3.bbclass: Use MACHINE for sysroot when not building for build host Khem Raj
2013-08-27 17:15 ` [PATCH 18/20] python3: Fix the compiler invocation and linker flags when cross compiling Khem Raj
2013-08-27 17:15 ` [PATCH 19/20] python: Add Patch description and status information Khem Raj
2013-08-27 17:15 ` [PATCH 20/20] python3_3.3.2.bb: Add liblzma to RDEPENDS for python3-misc Khem Raj
2013-08-27 17:49 ` Martin Jansa
2013-09-03 16:59 ` [PATCH V4 00/20] Add python 3 support Burton, Ross
2013-09-03 17:04 ` Khem Raj
2013-09-05 4:18 ` Khem Raj
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=1377629276.4083.101.camel@x121e.pbcl.net \
--to=pb@pbcl.net \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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