Re: [yocto] poky ref manual still confuses BB_ENV_WHITELIST and BB_ENV_EXTRAWHITE

2012-03-24 Thread Robert P. J. Day
On Fri, 23 Mar 2012, Rifenbark, Scott M wrote: Okay - I dug into this a bit with the help of Scott Garman. He uncovered a bit in the BitBake changelog. It states the following: By default it will now only pass certain whitelisted variables into the data store. If BB_PRESERVE_ENV is set

[yocto] tentative list of vars to be dropped from variable glossary

2012-03-24 Thread 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

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

2012-03-24 Thread 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:

[yocto] [PATCH] Documentation: Remove a number of dead variables from ref manual variable glossary.

2012-03-24 Thread Robert P. J. Day
Delete reference manual glossary entries of obviously dead/renamed variables: * PACKAGE_SUMMARY * PACKAGE_DESCRIPTION * POKY_EXTRA_INSTALL (renamed to CORE_IMAGE_EXTRA_INSTALL) * POKYMODE (renamed to TCMODE) * POKYLIBC (renamed to TCLIBC) * SHELLCMDS * TERMCMD * TERMCMDRUN In addition,

Re: [yocto] poky ref manual still confuses BB_ENV_WHITELIST and BB_ENV_EXTRAWHITE

2012-03-24 Thread Rifenbark, Scott M
It is worth noting and the state of the variables is being worked. I have several noted that I need to document. Understanding which ones are deprecated will be good too. Thanks for the diligence Robert. Scott -Original Message- From: Robert P. J. Day [mailto:rpj...@crashcourse.ca]

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

2012-03-24 Thread 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-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On Behalf

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

2012-03-24 Thread Rifenbark, Scott M
Ahhh... I need to read all the emails in my inbox before responding :) Thanks Richard. -Original Message- From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On Behalf Of Richard Purdie Sent: Saturday, March 24, 2012 5:53 AM To: Robert P. J. Day Cc: Yocto

Re: [yocto] pseudo interaction issue

2012-03-24 Thread Richard Purdie
On Fri, 2012-03-23 at 17:45 -0500, Peter Seebach wrote: On Fri, 23 Mar 2012 12:20:08 + Paul Eggleton paul.eggle...@linux.intel.com wrote: On Friday 23 March 2012 02:16:35 Peter Seebach wrote: Still really weird to me that I can't reproduce this outside of hob. I am pretty sure

Re: [yocto] pseudo interaction issue

2012-03-24 Thread Richard Purdie
On Sat, 2012-03-24 at 17:15 +, Richard Purdie wrote: What puzzles me is we get this value from envbackup[key] = os.environ.get(PSEUDO_PREFIX) so its already not in the environment. So basically if we read PSEUDO_PREFIX from the environment we get nothing. If we unset the value back to