From: Tim Bird <tim.bird@am.sony.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: Yocto discussion list <yocto@yoctoproject.org>
Subject: Re: might it be worth explaining BBMASK more comprehensively?
Date: Wed, 12 Dec 2012 12:33:32 -0800 [thread overview]
Message-ID: <50C8EA1C.9070804@am.sony.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1212121448150.13689@oneiric>
On 12/12/2012 11:53 AM, Robert P. J. Day wrote:
> On Wed, 12 Dec 2012, Tim Bird wrote:
>> I don't know if the .= with leading bar is the optimal
>> way to append on to BBMASK, but it seems fairly straightforward
>> to me. I sometimes use the leading ".*" and sometimes not.
>
> it doesn't seem like the leading ".*" makes any difference but
> that's the sort of detail that might confuse a reader and should be
> explained.
>
>> In my setup it seems to not be required, but maybe for flexibility
>> it should be used. I'm not sure -- it would depend on whether
>> python re.match or re.search is used for the regex.
Just to answer my own question...
In bitbake in poky-danny-8.0,
(poky-danny-8.0/bitbake/lib/bb/cooker.py)
bbmask_compiled.search() is used, which means that
the leading ".*" is unnecessary. A python re.search()
can match anywhere in the string, while a python re.match()
must match at the beginning of a string. Maybe previous
versions of bitbake used re.match()??
In any event, I would think that it should be considered
best practice to NOT include the leading ".*" in BBMASK
regex fragments.
-- Tim
=============================
Tim Bird
Architecture Group Chair, CE Workgroup of the Linux Foundation
Senior Staff Engineer, Sony Network Entertainment
=============================
next prev parent reply other threads:[~2012-12-12 20:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-12 19:27 might it be worth explaining BBMASK more comprehensively? Robert P. J. Day
2012-12-12 19:32 ` Rifenbark, Scott M
2012-12-12 19:37 ` Robert P. J. Day
2012-12-12 19:42 ` Tim Bird
2012-12-12 19:53 ` Robert P. J. Day
2012-12-12 20:20 ` Tim Bird
2012-12-12 20:33 ` Tim Bird [this message]
2012-12-12 19:54 ` Martin Jansa
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=50C8EA1C.9070804@am.sony.com \
--to=tim.bird@am.sony.com \
--cc=rpjday@crashcourse.ca \
--cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.