Re: [PATCH] Allow environment variables and ~ in bbconf paths

[Ed Bartosh <ed.bartosh@linux.intel.com>]

On Tue, Apr 14, 2015 at 02:33:41PM -0700, Christopher Larson wrote:
> On Tue, Apr 14, 2015 at 2:19 PM, Rifenbark, Scott M <
> scott.m.rifenbark@intel.com> wrote:
> 
> > Ed,
> >
> > This worked for me.... Thanks.
> >
> > Scott
> >
> > >-----Original Message-----
> > >From: Ed Bartosh [mailto:ed.bartosh@linux.intel.com]
> > >Sent: Tuesday, April 14, 2015 1:46 PM
> > >To: bitbake-devel@lists.openembedded.org
> > >Cc: Rifenbark, Scott M; Ed Bartosh
> > >Subject: [PATCH] Allow environment variables and ~ in bbconf paths
> > >
> > >This should allow to use ~, $HOME and other environment variables in
> > bbconf
> > >paths.
> > >
> > >Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com>
> >
> 
> We already have a mechanism by which environment variables flow into the
> metadata. Is there something wrong with using BB_ENV_EXTRAWHITE to use
> ${HOME} in this context?

Thank you for pointing out to this. However, I couldn't make this mechanism
to work for bbconf. I tried to set BB_PRESERVE_ENV, BB_ENV_WHITELIST and BB_ENV_EXTRAWHITE without any luck.
bitbake still crashes if HOME is used in bbconf.

--
Regards,
Ed