From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Matthew McClintock <msm@freescale.com>
Subject: Re: [PATCH] Nothing uses USERNAME, remove it - can cause sstate-cache conflicts
Date: Wed, 23 Nov 2011 16:50:39 -0800 [thread overview]
Message-ID: <4ECD94DF.6010506@linux.intel.com> (raw)
In-Reply-To: <1321569366-20167-1-git-send-email-msm@freescale.com>
On 11/17/2011 02:36 PM, Matthew McClintock wrote:
> USER is the correct variable to use, also this can affect sstate
> cache as well.
>
> Signed-off-by: Matthew McClintock<msm@freescale.com>
> ---
> I'm not 100% sure about this one but it seems like nothing is using this
> variable?
>
> Also one of my build machines (Jenkins specifically) was exporting
> USERNAME=root for some reason to the build environment. This was preventing
> sstate-cache from being used on other machines where it was not even
> defined/used AFAICT
>
> bitbake/lib/bb/utils.py | 1 -
> meta/conf/bitbake.conf | 2 +-
> 2 files changed, 1 insertions(+), 2 deletions(-)
>
> diff --git a/bitbake/lib/bb/utils.py b/bitbake/lib/bb/utils.py
> index 1f55407..bb3409d 100644
> --- a/bitbake/lib/bb/utils.py
> +++ b/bitbake/lib/bb/utils.py
> @@ -505,7 +505,6 @@ def preserved_envvars_exported():
> 'SHELL',
> 'TERM',
> 'USER',
> - 'USERNAME',
> ]
>
> def preserved_envvars_exported_interactive():
> diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
> index b7bcc23..b4335c9 100644
> --- a/meta/conf/bitbake.conf
> +++ b/meta/conf/bitbake.conf
> @@ -751,7 +751,7 @@ TRANSLATED_TARGET_ARCH ??= "${@d.getVar('TARGET_ARCH', True).replace("_", "-")}"
> # Setup our default hash policy
> BB_SIGNATURE_HANDLER ?= "basic"
> BB_HASHTASK_WHITELIST ?= "(.*-cross$|.*-native$|.*-cross-initial$|.*-cross-intermediate$|^virtual:native:.*|^virtual:nativesdk:.*)"
> -BB_HASHBASE_WHITELIST ?= "TMPDIR FILE PATH PWD BB_TASKHASH BBPATH DL_DIR SSTATE_DIR THISDIR FILESEXTRAPATHS FILE_DIRNAME HOME LOGNAME SHELL TERM USER FILESPATH USERNAME STAGING_DIR_HOST STAGING_DIR_TARGET COREBASE"
> +BB_HASHBASE_WHITELIST ?= "TMPDIR FILE PATH PWD BB_TASKHASH BBPATH DL_DIR SSTATE_DIR THISDIR FILESEXTRAPATHS FILE_DIRNAME HOME LOGNAME SHELL TERM USER FILESPATH STAGING_DIR_HOST STAGING_DIR_TARGET COREBASE"
>
> MLPREFIX ??= ""
> MULTILIB_VARIANTS ??= ""
This should really be 2 patches, I know they are small, but they should
be broken down.
Thanks
Sau!
next prev parent reply other threads:[~2011-11-24 0:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-17 22:36 [PATCH] Nothing uses USERNAME, remove it - can cause sstate-cache conflicts Matthew McClintock
2011-11-24 0:50 ` Saul Wold [this message]
2011-11-24 1:12 ` Matthew McClintock
2011-11-25 0:30 ` Richard Purdie
-- strict thread matches above, loose matches on Subject: below --
2011-11-24 1:11 Matthew McClintock
2011-11-25 0:29 ` Richard Purdie
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=4ECD94DF.6010506@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=msm@freescale.com \
--cc=openembedded-core@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.