From: Andreas Oberritter <obi@opendreambox.org>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 3/3] scripts/bitbake: add/fix some comments
Date: Tue, 27 Mar 2012 15:09:35 +0200 [thread overview]
Message-ID: <4F71BC0F.6060905@opendreambox.org> (raw)
In-Reply-To: <198e1157afad1418826484e4044f59c7741b57f9.1332848153.git.paul.eggleton@linux.intel.com>
On 27.03.2012 13:50, Paul Eggleton wrote:
> Add some comments explaining what this script does, fix one grammatical
> error in a comment and make the tar-replacement-native comment give the
> full reason why it is needed.
>
> Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Acked-by: Andreas Oberritter <obi@opendreambox.org>
> ---
> scripts/bitbake | 16 +++++++++++++---
> 1 files changed, 13 insertions(+), 3 deletions(-)
>
> diff --git a/scripts/bitbake b/scripts/bitbake
> index f02e89b..a8adeb7 100755
> --- a/scripts/bitbake
> +++ b/scripts/bitbake
> @@ -1,10 +1,20 @@
> #!/bin/sh
>
> +# This is the bitbake wrapper script that ensures everything is set up
> +# correctly in the environment, builds pseudo separately if it hasn't
> +# already been built, and then runs bitbake within pseudo.
> +
> export BBFETCH2=True
> export BB_ENV_EXTRAWHITE="PSEUDO_BUILD PSEUDO_DISABLED $BB_ENV_EXTRAWHITE"
>
> +# For certain operations (i.e. that won't be actually running any tasks)
> +# we don't need pseudo
> NO_BUILD_OPTS="--version -h --help -p --parse-only -s --show-versions -e --environment -g --graphviz"
> +
> +# Some options are useful to pass through to the initial pseudo build if
> +# that needs to be run (for debugging)
> PASSTHROUGH_OPTS="-D -DD -DDD -DDDD -v"
> +
> needpseudo="1"
> for opt in $@; do
> for key in $NO_BUILD_OPTS; do
> @@ -29,7 +39,7 @@ if [ "$py_v3_check" != "" ]; then
> fi
>
> # Similarly, we now have code that doesn't parse correctly with older
> -# versions of Python, and rather than fixing that and be eternally
> +# versions of Python, and rather than fixing that and being eternally
> # vigilant for any other new feature use, just check the version here.
> py_v26_check=`python -c 'import sys; print sys.version_info >= (2,6,0)'`
> if [ "$py_v26_check" != "True" ]; then
> @@ -53,8 +63,8 @@ float_test() {
> echo | awk 'END { exit ( !( '"$1"')); }'
> }
>
> -# Tar version 1.24 and onwards handle symlinks in sstate packages correctly
> -# but earlier versions do not
> +# Tar version 1.24 and onwards handle overwriting symlinks correctly
> +# but earlier versions do not; this needs to work properly for sstate
> float_test "$TARVERSION > 1.23" && needtar="0"
>
> buildpseudo="1"
next prev parent reply other threads:[~2012-03-27 13:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-27 11:50 [PATCH 0/3] Fixes for bitbake wrapper script Paul Eggleton
2012-03-27 11:50 ` [PATCH 1/3] scripts/bitbake: try harder to check if pseudo exists Paul Eggleton
2012-03-27 13:08 ` Andreas Oberritter
2012-03-27 13:14 ` Paul Eggleton
2012-03-27 11:50 ` [PATCH 2/3] scripts/bitbake: allow switching between build directories Paul Eggleton
2012-03-27 13:09 ` Andreas Oberritter
2012-03-27 11:50 ` [PATCH 3/3] scripts/bitbake: add/fix some comments Paul Eggleton
2012-03-27 13:09 ` Andreas Oberritter [this message]
2012-03-31 15:45 ` [PATCH 0/3] Fixes for bitbake wrapper script Paul Eggleton
2012-04-03 23:33 ` Saul Wold
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=4F71BC0F.6060905@opendreambox.org \
--to=obi@opendreambox.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox