All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Lock <josh@linux.intel.com>
To: bitbake-devel@lists.openembedded.org
Subject: [RFC PATCH 0/1] Save the initial environment
Date: Mon, 18 Jul 2011 15:33:16 -0700	[thread overview]
Message-ID: <cover.1311028023.git.josh@linux.intel.com> (raw)

Both Chris' terminal work and my reparse command will benefit from a saved
copy of the initial enviornment. The Python docs indicate that the os.environ
map is captured when the os module is first imported
http://docs.python.org/library/os.html#os.environ) so this patch adds a
variable to the bb namespace (bb.initial_environ) that is an early copy of
the environment.

I put the variable here so that a) it's easily accessible and b) we can take
the copy pretty early on.

Any thoughts on this? Note the RFC prefix. :-)

Thanks,

Joshua

Please review the following changes for suitability for inclusion. If you have
any objections or suggestions for improvement, please respond to the patches. If
you agree with the changes, please provide your Acked-by.

The following changes since commit 5c8eeefc79455f058dda8f04cf4c12dc5418e00f:

  cooker: only return *Found events if something was actually found (2011-07-14 15:12:40 +0100)

are available in the git repository at:
  git://github.com/incandescant/bitbake initialenv
  https://github.com/incandescant/bitbake/tree/initialenv

Joshua Lock (1):
  lib/bb: preserve a copy of the initial environment variables

 lib/bb/__init__.py |    4 ++++
 1 files changed, 4 insertions(+), 0 deletions(-)

-- 
1.7.6




             reply	other threads:[~2011-07-18 22:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-18 22:33 Joshua Lock [this message]
2011-07-18 22:33 ` [RFC PATCH 1/1] lib/bb: preserve a copy of the initial environment variables Joshua Lock
2011-07-21 21:22 ` [RFC PATCH 0/1] Save the initial environment Richard Purdie
2011-07-21 22:12   ` Joshua Lock

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=cover.1311028023.git.josh@linux.intel.com \
    --to=josh@linux.intel.com \
    --cc=bitbake-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.