All of lore.kernel.org
 help / color / mirror / Atom feed
From: Holger Freyther <zecke@selfish.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Creating a pristine environment?
Date: Tue, 13 May 2008 10:43:50 +0200	[thread overview]
Message-ID: <200805131043.50899.zecke@selfish.org> (raw)
In-Reply-To: <g044dn$kot$1@ger.gmane.org>

On Saturday 10 May 2008 14:28:39 Koen Kooi wrote:
> Holger Freyther wrote:
> > Okay. I added an option, I clean the environment after having parsed the
> > configuration. This means everything used from conf/local.conf (TOPDIR,
> > BBPATH, BBFILES, MACHINE...) will be inside the configuration data of
> > bitbake but not be exported.
>
> Implementation question: who will fix all the shell based functions in
> OE that rely on things like MACHINE being exported?

To my understanding there is nothing to fix. Bitbake will unexport the 
environment after having parsed the configuration. If you have export FOO 
inside a Bitbake file. data.py:emit_var will put an "export FOO=.." into the 
shell script.

comments.

	z.



  reply	other threads:[~2008-05-13  8:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-08  0:15 Creating a pristine environment? Holger Freyther
2008-05-08 10:05 ` Koen Kooi
2008-05-08 11:06   ` Holger Freyther
2008-05-08 11:29     ` Richard Purdie
2008-05-08 12:51       ` Mark Brown
2008-05-10 12:05       ` Holger Freyther
2008-05-10 12:28         ` Koen Kooi
2008-05-13  8:43           ` Holger Freyther [this message]
2008-05-13 10:42             ` Rolf Leggewie
2008-05-19 21:15         ` Richard Purdie
2008-05-21 21:38           ` Richard Purdie
2008-05-08 12:06 ` Cliff Brake
2008-05-08 12:14   ` Leon Woestenberg
2008-05-08 13:57     ` Cliff Brake
2008-05-08 14:10 ` Geoffrey Wossum
2008-05-09  8:55 ` Leon Woestenberg

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=200805131043.50899.zecke@selfish.org \
    --to=zecke@selfish.org \
    --cc=openembedded-devel@lists.openembedded.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.