tentative list of vars to be dropped from variable glossary

tentative list of vars to be dropped from variable glossary

[Robert P. J. Day]

  finished perusing ref manual variable glossary and here's my list of
variables that would appear to be dead and should be dropped from the
glossary:

http://www.crashcourse.ca/wiki/index.php/OE-Core#Dead.28.3F.29_variables.2C_to_be_dropped_from_glossary

unless there are objections or anyone has any others to add to that
list, i'll submit a patch that removes all those entries.

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

Re: tentative list of vars to be dropped from variable glossary

[Richard Purdie]

On Sat, 2012-03-24 at 05:27 -0400, Robert P. J. Day wrote:
> finished perusing ref manual variable glossary and here's my list of
> variables that would appear to be dead and should be dropped from the
> glossary:
> 
> http://www.crashcourse.ca/wiki/index.php/OE-Core#Dead.28.3F.29_variables.2C_to_be_dropped_from_glossary
> 
> unless there are objections or anyone has any others to add to that
> list, i'll submit a patch that removes all those entries.


PACKAGE_SUMMARY - delete
PACKAGE_DESCRIPTION - delete
POKY_EXTRA_INSTALL - was renamed to CORE_IMAGE_EXTRA_INSTALL
POKYMODE -> rename TCMODE
POKYLIBC -> rename TCLIBC
SHELLCMDS - delete
TERMCMD - delete
TERMCMDRUN - delete

Cheers,

Richard

Re: tentative list of vars to be dropped from variable glossary

[Rifenbark, Scott M]

We should have Richard Purdie view and comment on this list before a patch is applied to remove them.  He has voiced concern in the past for completely removing variables.  

Scott

-----Original Message-----
From: yocto-bounces@yoctoproject.org [mailto:yocto-bounces@yoctoproject.org] On Behalf Of Robert P. J. Day
Sent: Saturday, March 24, 2012 3:27 AM
To: Yocto discussion list
Subject: [yocto] tentative list of vars to be dropped from variable glossary


  finished perusing ref manual variable glossary and here's my list of
variables that would appear to be dead and should be dropped from the
glossary:

http://www.crashcourse.ca/wiki/index.php/OE-Core#Dead.28.3F.29_variables.2C_to_be_dropped_from_glossary

unless there are objections or anyone has any others to add to that
list, i'll submit a patch that removes all those entries.

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

Re: tentative list of vars to be dropped from variable glossary

[Rifenbark, Scott M]

Ahhh...  I need to read all the emails in my inbox before responding :)

Thanks Richard.

-----Original Message-----
From: yocto-bounces@yoctoproject.org [mailto:yocto-bounces@yoctoproject.org] On Behalf Of Richard Purdie
Sent: Saturday, March 24, 2012 5:53 AM
To: Robert P. J. Day
Cc: Yocto discussion list
Subject: Re: [yocto] tentative list of vars to be dropped from variable glossary

On Sat, 2012-03-24 at 05:27 -0400, Robert P. J. Day wrote:
> finished perusing ref manual variable glossary and here's my list of
> variables that would appear to be dead and should be dropped from the
> glossary:
> 
> http://www.crashcourse.ca/wiki/index.php/OE-Core#Dead.28.3F.29_variables.2C_to_be_dropped_from_glossary
> 
> unless there are objections or anyone has any others to add to that
> list, i'll submit a patch that removes all those entries.


PACKAGE_SUMMARY - delete
PACKAGE_DESCRIPTION - delete
POKY_EXTRA_INSTALL - was renamed to CORE_IMAGE_EXTRA_INSTALL
POKYMODE -> rename TCMODE
POKYLIBC -> rename TCLIBC
SHELLCMDS - delete
TERMCMD - delete
TERMCMDRUN - delete

Cheers,

Richard



_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: tentative list of vars to be dropped from variable glossary

[Rudolf Streif]

[-- Attachment #1: Type: text/plain, Size: 694 bytes --]

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.

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?

Rudi

[-- Attachment #2: Type: text/html, Size: 773 bytes --]

Re: tentative list of vars to be dropped from variable glossary

[Richard Purdie]

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

Re: tentative list of vars to be dropped from variable glossary

[Rudolf Streif]

[-- Attachment #1: Type: text/plain, Size: 1179 bytes --]

Thanks, Richard. Clearer now but not entirely.


> >> 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.
>
> Yes, it removes it from being parsed. I used, for test although not
sensible, BBMASK = "base-passwd". If I then tried building
core-image-minimal it fails with "Nothing provides base-passwd". If one
could use BBMASK to customize images as suggested in
http://www.yoctoproject.org/docs/latest/dev-manual/dev-manual.html#usingpoky-extend-customimage-localconf
then
one would expect the package to be removed indirectly from the image.
However, that does not happen, the build just fails.


>
> >> 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.
>

That use case makes sense. If I know that I don't include certain packages
like *gpe* in the images I am building then I can speed up the
build/parsing process by masking the recipes and therefore the regular
expression syntax makes perfectly sense.

Thanks,
Rudi

[-- Attachment #2: Type: text/html, Size: 1769 bytes --]

Re: tentative list of vars to be dropped from variable glossary

[Richard Purdie]

On Mon, 2012-03-26 at 16:50 -0700, Rudolf Streif wrote:
> Thanks, Richard. Clearer now but not entirely.
> 
>         
>         
>         >> 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.
>         
>         
> Yes, it removes it from being parsed. I used, for test although not
> sensible, BBMASK = "base-passwd". If I then tried building
> core-image-minimal it fails with "Nothing provides base-passwd". If
> one could use BBMASK to customize images as suggested
> in http://www.yoctoproject.org/docs/latest/dev-manual/dev-manual.html#usingpoky-extend-customimage-localconf then one would expect the package to be removed indirectly from the image. However, that does not happen, the build just fails.

I hadn't realised Scott had added this to the customising images section
of the manual. This is not what its designed for and we need to move
this to somewhere less confusing.

Scott: This is going to need to move somewhere else in the manual as
this is confusing. I'm going to suggest a 4.12 section "Other tips and
tricks" which says:

"""
Sometimes there are groups of recipes you might wish to filter out. If
there were recipes you know you're never going to want/use, removing
them from parsing would speed up parts of the build for example.

It is possible to filter or mask out both .bb and .bbappend files. You
can do this by providing an expression with the BBMASK variable. Here is
an example:

     BBMASK = ".*/meta-mymachine/recipes-maybe/"

Here, all .bb and .bbappend files in the directory that matches the
expression are ignored during the build process. 
"""

Cheers,

Richard

Re: tentative list of vars to be dropped from variable glossary

[Rifenbark, Scott M]

I will take care of this. 

Scott

-----Original Message-----
From: Richard Purdie [mailto:richard.purdie@linuxfoundation.org] 
Sent: Thursday, March 29, 2012 6:48 AM
To: Rudolf Streif; Rifenbark, Scott M
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] tentative list of vars to be dropped from variable glossary

On Mon, 2012-03-26 at 16:50 -0700, Rudolf Streif wrote:
> Thanks, Richard. Clearer now but not entirely.
> 
>         
>         
>         >> 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.
>         
>         
> Yes, it removes it from being parsed. I used, for test although not
> sensible, BBMASK = "base-passwd". If I then tried building
> core-image-minimal it fails with "Nothing provides base-passwd". If
> one could use BBMASK to customize images as suggested
> in http://www.yoctoproject.org/docs/latest/dev-manual/dev-manual.html#usingpoky-extend-customimage-localconf then one would expect the package to be removed indirectly from the image. However, that does not happen, the build just fails.

I hadn't realised Scott had added this to the customising images section
of the manual. This is not what its designed for and we need to move
this to somewhere less confusing.

Scott: This is going to need to move somewhere else in the manual as
this is confusing. I'm going to suggest a 4.12 section "Other tips and
tricks" which says:

"""
Sometimes there are groups of recipes you might wish to filter out. If
there were recipes you know you're never going to want/use, removing
them from parsing would speed up parts of the build for example.

It is possible to filter or mask out both .bb and .bbappend files. You
can do this by providing an expression with the BBMASK variable. Here is
an example:

     BBMASK = ".*/meta-mymachine/recipes-maybe/"

Here, all .bb and .bbappend files in the directory that matches the
expression are ignored during the build process. 
"""

Cheers,

Richard