All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Cc: bitbake-dev@lists.berlios.de
Subject: Re: Creating a pristine environment?
Date: Thu, 08 May 2008 12:05:38 +0200	[thread overview]
Message-ID: <fvuj9i$nt9$1@ger.gmane.org> (raw)
In-Reply-To: <200805080215.23729.zecke@selfish.org>

Holger Freyther wrote:
> Hey,
>
> I have seen raster's environment breaking various buildsystems and we might
> want to really start having a clean environment before starting to build.
>
> the patch below should implement it. Should we do this in OE? I'm aware of the
> unexport inside OE but we really should do this the otherway around.

While this is a good idea, your current implementation breaks:

MACHINE=foo ANGSTROM_MODE=bar bitbake foo-bar-image


>
>
> comments?
>
> 	z.
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel





  reply	other threads:[~2008-05-08 10:06 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 [this message]
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
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='fvuj9i$nt9$1@ger.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --cc=bitbake-dev@lists.berlios.de \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@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.