* might it be worth explaining BBMASK more comprehensively?
@ 2012-12-12 19:27 Robert P. J. Day
2012-12-12 19:32 ` Rifenbark, Scott M
2012-12-12 19:42 ` Tim Bird
0 siblings, 2 replies; 8+ messages in thread
From: Robert P. J. Day @ 2012-12-12 19:27 UTC (permalink / raw)
To: Yocto discussion list
a bit more pedantry, but is there a more complete example of the use
of BBMASK than the trivial example in the ref and dev manuals?
the ref manual provides this example by way of explanation:
BBMASK = ".*/meta-ti/recipes-misc/"
well, ok, except you occasinally find slight variations like:
BBMASK = "meta-ti/recipes-misc/"
or
BBMASK = "meta-ti/recipes-misc"
given that there are places where a trailing slash is significant,
are all of the above exactly equivalent? if so, that's worth noting.
also, what about an example showing masking out a couple
directories, or perhaps a single recipe from a layer, and so on? at
the moment, the manuals suggest you can mask multiple recipes but
nowhere do i see the reader being given an actual example of how to do
that.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: might it be worth explaining BBMASK more comprehensively?
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
1 sibling, 1 reply; 8+ messages in thread
From: Rifenbark, Scott M @ 2012-12-12 19:32 UTC (permalink / raw)
To: Robert P. J. Day, Yocto discussion list
Please feel free (anyone) to provide some useful examples and a bit of explanation for each and I will be happy to get them in the manual(s).
Scott
>-----Original Message-----
>From: yocto-bounces@yoctoproject.org [mailto:yocto-
>bounces@yoctoproject.org] On Behalf Of Robert P. J. Day
>Sent: Wednesday, December 12, 2012 11:27 AM
>To: Yocto discussion list
>Subject: [yocto] might it be worth explaining BBMASK more
>comprehensively?
>
>
> a bit more pedantry, but is there a more complete example of the use
>of BBMASK than the trivial example in the ref and dev manuals?
>
> the ref manual provides this example by way of explanation:
>
>BBMASK = ".*/meta-ti/recipes-misc/"
>
>well, ok, except you occasinally find slight variations like:
>
>BBMASK = "meta-ti/recipes-misc/"
>
>or
>
>BBMASK = "meta-ti/recipes-misc"
>
> given that there are places where a trailing slash is significant,
>are all of the above exactly equivalent? if so, that's worth noting.
>
> also, what about an example showing masking out a couple
>directories, or perhaps a single recipe from a layer, and so on? at
>the moment, the manuals suggest you can mask multiple recipes but
>nowhere do i see the reader being given an actual example of how to do
>that.
>
>rday
>
>--
>
>========================================================================
>Robert P. J. Day Ottawa, Ontario, CANADA
> http://crashcourse.ca
>
>Twitter: http://twitter.com/rpjday
>LinkedIn: http://ca.linkedin.com/in/rpjday
>========================================================================
>_______________________________________________
>yocto mailing list
>yocto@yoctoproject.org
>https://lists.yoctoproject.org/listinfo/yocto
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: might it be worth explaining BBMASK more comprehensively?
2012-12-12 19:32 ` Rifenbark, Scott M
@ 2012-12-12 19:37 ` Robert P. J. Day
0 siblings, 0 replies; 8+ messages in thread
From: Robert P. J. Day @ 2012-12-12 19:37 UTC (permalink / raw)
To: Rifenbark, Scott M; +Cc: Yocto discussion list
On Wed, 12 Dec 2012, Rifenbark, Scott M wrote:
> Please feel free (anyone) to provide some useful examples and a bit
> of explanation for each and I will be happy to get them in the
> manual(s).
i forgot to mention this snippet i ran across in the meta-angstrom
layer's contrib/local.conf:
BBFILES := "/OE/org.openembedded.dev/recipes/*/*.bb"
BBMASK = ""
that combination isn't something that appears to be explained anywhere
and some readers might wonder what it means to explicitly set BBFILES
and clear BBMASK.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: might it be worth explaining BBMASK more comprehensively?
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:42 ` Tim Bird
2012-12-12 19:53 ` Robert P. J. Day
2012-12-12 19:54 ` Martin Jansa
1 sibling, 2 replies; 8+ messages in thread
From: Tim Bird @ 2012-12-12 19:42 UTC (permalink / raw)
To: Robert P. J. Day; +Cc: Yocto discussion list
On 12/12/2012 11:27 AM, Robert P. J. Day wrote:
>
> a bit more pedantry, but is there a more complete example of the use
> of BBMASK than the trivial example in the ref and dev manuals?
>
> the ref manual provides this example by way of explanation:
>
> BBMASK = ".*/meta-ti/recipes-misc/"
>
> well, ok, except you occasinally find slight variations like:
>
> BBMASK = "meta-ti/recipes-misc/"
>
> or
>
> BBMASK = "meta-ti/recipes-misc"
>
> given that there are places where a trailing slash is significant,
> are all of the above exactly equivalent? if so, that's worth noting.
>
> also, what about an example showing masking out a couple
> directories, or perhaps a single recipe from a layer, and so on? at
> the moment, the manuals suggest you can mask multiple recipes but
> nowhere do i see the reader being given an actual example of how to do
> that.
Indeed. These would be good clarifications. The manual says that
this is a single python regular expression. Hence, when masking multiple
directories or recipes, you use a vertical bar to separate the regex fragments.
Here's a particularly complex case I used once:
BBMASK = "meta-ti/recipes-misc|meta-ti/recipes-ti/packagegroup"
BBMASK .= "|.*meta-oe/recipes-support"
#BBMASK .= "|.*openldap"
#BBMASK .= "|.*opencv"
#BBMASK .= "|.*lzma"
BBMASK .= "|meta-oe/recipes-core/packagegroups"
BBMASK .= "|meta-oe/recipes-devtools"
BBMASK .= "|meta-oe/recipes-extended"
BBMASK .= "|meta-oe/recipes-multimedia"
BBMASK .= "|meta-oe/recipes-navigation"
BBMASK .= "|meta-oe/recipes-connectivity"
BBMASK .= "|meta-oe/recipes-graphics"
BBMASK .= "|meta-oe/recipes-qt"
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.
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 wheter
python re.match or re.search is used for the regex.
-- Tim
=============================
Tim Bird
Architecture Group Chair, CE Workgroup of the Linux Foundation
Senior Staff Engineer, Sony Network Entertainment
=============================
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: might it be worth explaining BBMASK more comprehensively?
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
2012-12-12 19:54 ` Martin Jansa
1 sibling, 2 replies; 8+ messages in thread
From: Robert P. J. Day @ 2012-12-12 19:53 UTC (permalink / raw)
To: Tim Bird; +Cc: Yocto discussion list
On Wed, 12 Dec 2012, Tim Bird wrote:
> On 12/12/2012 11:27 AM, Robert P. J. Day wrote:
> >
> > a bit more pedantry, but is there a more complete example of the use
> > of BBMASK than the trivial example in the ref and dev manuals?
> >
> > the ref manual provides this example by way of explanation:
> >
> > BBMASK = ".*/meta-ti/recipes-misc/"
> >
> > well, ok, except you occasinally find slight variations like:
> >
> > BBMASK = "meta-ti/recipes-misc/"
> >
> > or
> >
> > BBMASK = "meta-ti/recipes-misc"
> >
> > given that there are places where a trailing slash is significant,
> > are all of the above exactly equivalent? if so, that's worth noting.
> >
> > also, what about an example showing masking out a couple
> > directories, or perhaps a single recipe from a layer, and so on? at
> > the moment, the manuals suggest you can mask multiple recipes but
> > nowhere do i see the reader being given an actual example of how to do
> > that.
>
> Indeed. These would be good clarifications. The manual says that
> this is a single python regular expression. Hence, when masking multiple
> directories or recipes, you use a vertical bar to separate the regex fragments.
>
> Here's a particularly complex case I used once:
> BBMASK = "meta-ti/recipes-misc|meta-ti/recipes-ti/packagegroup"
> BBMASK .= "|.*meta-oe/recipes-support"
> #BBMASK .= "|.*openldap"
> #BBMASK .= "|.*opencv"
> #BBMASK .= "|.*lzma"
> BBMASK .= "|meta-oe/recipes-core/packagegroups"
> BBMASK .= "|meta-oe/recipes-devtools"
> BBMASK .= "|meta-oe/recipes-extended"
> BBMASK .= "|meta-oe/recipes-multimedia"
> BBMASK .= "|meta-oe/recipes-navigation"
> BBMASK .= "|meta-oe/recipes-connectivity"
> BBMASK .= "|meta-oe/recipes-graphics"
> BBMASK .= "|meta-oe/recipes-qt"
>
> 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 wheter
> python re.match or re.search is used for the regex.
> -- Tim
from your examples above, is this how you mask individual software
recipes?
BBMASK .= "|.*openldap"
that's kind of useful to know.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: might it be worth explaining BBMASK more comprehensively?
2012-12-12 19:53 ` Robert P. J. Day
@ 2012-12-12 20:20 ` Tim Bird
2012-12-12 20:33 ` Tim Bird
1 sibling, 0 replies; 8+ messages in thread
From: Tim Bird @ 2012-12-12 20:20 UTC (permalink / raw)
To: Robert P. J. Day; +Cc: Yocto discussion list
On 12/12/2012 11:53 AM, Robert P. J. Day wrote:
> On Wed, 12 Dec 2012, Tim Bird wrote:
>
>> On 12/12/2012 11:27 AM, Robert P. J. Day wrote:
>>>
>>> a bit more pedantry, but is there a more complete example of the use
>>> of BBMASK than the trivial example in the ref and dev manuals?
>>>
>>> the ref manual provides this example by way of explanation:
>>>
>>> BBMASK = ".*/meta-ti/recipes-misc/"
>>>
>>> well, ok, except you occasinally find slight variations like:
>>>
>>> BBMASK = "meta-ti/recipes-misc/"
>>>
>>> or
>>>
>>> BBMASK = "meta-ti/recipes-misc"
>>>
>>> given that there are places where a trailing slash is significant,
>>> are all of the above exactly equivalent? if so, that's worth noting.
>>>
>>> also, what about an example showing masking out a couple
>>> directories, or perhaps a single recipe from a layer, and so on? at
>>> the moment, the manuals suggest you can mask multiple recipes but
>>> nowhere do i see the reader being given an actual example of how to do
>>> that.
>>
>> Indeed. These would be good clarifications. The manual says that
>> this is a single python regular expression. Hence, when masking multiple
>> directories or recipes, you use a vertical bar to separate the regex fragments.
>>
>> Here's a particularly complex case I used once:
>> BBMASK = "meta-ti/recipes-misc|meta-ti/recipes-ti/packagegroup"
>> BBMASK .= "|.*meta-oe/recipes-support"
>> #BBMASK .= "|.*openldap"
>> #BBMASK .= "|.*opencv"
>> #BBMASK .= "|.*lzma"
>> BBMASK .= "|meta-oe/recipes-core/packagegroups"
>> BBMASK .= "|meta-oe/recipes-devtools"
>> BBMASK .= "|meta-oe/recipes-extended"
>> BBMASK .= "|meta-oe/recipes-multimedia"
>> BBMASK .= "|meta-oe/recipes-navigation"
>> BBMASK .= "|meta-oe/recipes-connectivity"
>> BBMASK .= "|meta-oe/recipes-graphics"
>> BBMASK .= "|meta-oe/recipes-qt"
>>
>> 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 wheter
>> python re.match or re.search is used for the regex.
>
>> -- Tim
>
> from your examples above, is this how you mask individual software
> recipes?
>
> BBMASK .= "|.*openldap"
>
> that's kind of useful to know.
That's how I do it. I'm not sure if there's some other preferred
method or not. This should catch that name in all layers.
-- Tim
=============================
Tim Bird
Architecture Group Chair, CE Workgroup of the Linux Foundation
Senior Staff Engineer, Sony Network Entertainment
=============================
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: might it be worth explaining BBMASK more comprehensively?
2012-12-12 19:53 ` Robert P. J. Day
2012-12-12 20:20 ` Tim Bird
@ 2012-12-12 20:33 ` Tim Bird
1 sibling, 0 replies; 8+ messages in thread
From: Tim Bird @ 2012-12-12 20:33 UTC (permalink / raw)
To: Robert P. J. Day; +Cc: Yocto discussion list
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
=============================
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: might it be worth explaining BBMASK more comprehensively?
2012-12-12 19:42 ` Tim Bird
2012-12-12 19:53 ` Robert P. J. Day
@ 2012-12-12 19:54 ` Martin Jansa
1 sibling, 0 replies; 8+ messages in thread
From: Martin Jansa @ 2012-12-12 19:54 UTC (permalink / raw)
To: Tim Bird; +Cc: Yocto discussion list
[-- Attachment #1: Type: text/plain, Size: 2124 bytes --]
On Wed, Dec 12, 2012 at 11:42:41AM -0800, Tim Bird wrote:
> On 12/12/2012 11:27 AM, Robert P. J. Day wrote:
> >
> > a bit more pedantry, but is there a more complete example of the use
> > of BBMASK than the trivial example in the ref and dev manuals?
> >
> > the ref manual provides this example by way of explanation:
> >
> > BBMASK = ".*/meta-ti/recipes-misc/"
> >
> > well, ok, except you occasinally find slight variations like:
> >
> > BBMASK = "meta-ti/recipes-misc/"
> >
> > or
> >
> > BBMASK = "meta-ti/recipes-misc"
> >
> > given that there are places where a trailing slash is significant,
> > are all of the above exactly equivalent? if so, that's worth noting.
> >
> > also, what about an example showing masking out a couple
> > directories, or perhaps a single recipe from a layer, and so on? at
> > the moment, the manuals suggest you can mask multiple recipes but
> > nowhere do i see the reader being given an actual example of how to do
> > that.
>
> Indeed. These would be good clarifications. The manual says that
> this is a single python regular expression. Hence, when masking multiple
> directories or recipes, you use a vertical bar to separate the regex fragments.
>
> Here's a particularly complex case I used once:
> BBMASK = "meta-ti/recipes-misc|meta-ti/recipes-ti/packagegroup"
> BBMASK .= "|.*meta-oe/recipes-support"
> #BBMASK .= "|.*openldap"
> #BBMASK .= "|.*opencv"
> #BBMASK .= "|.*lzma"
> BBMASK .= "|meta-oe/recipes-core/packagegroups"
> BBMASK .= "|meta-oe/recipes-devtools"
> BBMASK .= "|meta-oe/recipes-extended"
> BBMASK .= "|meta-oe/recipes-multimedia"
> BBMASK .= "|meta-oe/recipes-navigation"
> BBMASK .= "|meta-oe/recipes-connectivity"
> BBMASK .= "|meta-oe/recipes-graphics"
> BBMASK .= "|meta-oe/recipes-qt"
>
> I don't know if the .= with leading bar is the optimal
> way to append on to BBMASK, but it seems fairly straightforward
Yes because += would add extra space and break regexp (_append should
probably work too).
Cheers,
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2012-12-12 20:31 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2012-12-12 19:54 ` Martin Jansa
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.