All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Rudolf Streif <rudolf.streif@linux.com>
Cc: yocto@yoctoproject.org
Subject: Re: tentative list of vars to be dropped from variable glossary
Date: Mon, 26 Mar 2012 23:58:04 +0100	[thread overview]
Message-ID: <1332802684.28414.146.camel@ted> (raw)
In-Reply-To: <CA+gsK-raRiKQ7GHLSy4tAJHJmDardhr8by0A9FGJ7diCYo00Uw@mail.gmail.com>

On Mon, 2012-03-26 at 12:42 -0700, Rudolf Streif wrote:
> Another variable that seems to be dropped from the latest 1.1.1
> revision of the Reference Manual is BBMASK. In previous versions of
> the manual it was explained that this variable can be used to remove
> packages from images. However, that did not work for me and it did not
> surprise me either. 

BBMASK removes recipes from being parsed. It does not remove them from
images although that would I guess be an indirect result since you could
no longer build them.

> To include a package with an image you will have to make it a
> dependency of that image. If you then hide the recipe of the package
> using BBMASK then you are breaking the dependency and the Bitbake will
> complain with "Nothing provides <package>" because the dependency is
> still there.
>
> I could not think of any other use case for BBMASK in the way it is
> implemented. Are there any?

Its designed so that if you for example didn't care out any *gpe*
recipe, you could exclude them entirely and not even have the parse
overhead.

Its less useful now things are split into layers but nonetheless still
valid syntax.

Cheers,

Richard



  reply	other threads:[~2012-03-26 22:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-24  9:27 tentative list of vars to be dropped from variable glossary Robert P. J. Day
2012-03-24 11:52 ` Richard Purdie
2012-03-24 12:56   ` Rifenbark, Scott M
2012-03-26 19:42     ` Rudolf Streif
2012-03-26 22:58       ` Richard Purdie [this message]
2012-03-26 23:50         ` Rudolf Streif
2012-03-29 12:47           ` Richard Purdie
2012-03-29 13:32             ` Rifenbark, Scott M
2012-03-24 12:55 ` Rifenbark, Scott M

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=1332802684.28414.146.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=rudolf.streif@linux.com \
    --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.