From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Cc: Alexander Kanavin <alex@linutronix.de>
Subject: RE: [OE-core] [PATCH 1/2] scripts/oe-setup-builddir: copy site.conf.sample out of template directories (if it exists)
Date: Thu, 7 Jul 2022 13:26:21 +0000 [thread overview]
Message-ID: <d04fa3ca7398489a99f8356b17f1174a@axis.com> (raw)
In-Reply-To: <20220706182329.3085564-1-alex@linutronix.de>
> -----Original Message-----
> From: openembedded-core@lists.openembedded.org <openembedded-
> core@lists.openembedded.org> On Behalf Of Alexander Kanavin
> Sent: den 6 juli 2022 20:23
> To: openembedded-core@lists.openembedded.org
> Cc: Alexander Kanavin <alex@linutronix.de>
> Subject: [OE-core] [PATCH 1/2] scripts/oe-setup-builddir: copy
> site.conf.sample out of template directories (if it exists)
>
> This allows:
>
> 1. Showing users where and how to define these settings correctly when setting up
> a build from templates in poky (meta-poky/conf/site.conf.sample has commented
> out examples and was previously unused).
>
> 2. Distributing site-specific settings with template configurations in other layers,
> so there's no need to set them up separately.
>
> Signed-off-by: Alexander Kanavin <alex@linutronix.de>
> ---
> scripts/oe-setup-builddir | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/scripts/oe-setup-builddir b/scripts/oe-setup-builddir
> index 54048e62ec..5ad6dd4138 100755
> --- a/scripts/oe-setup-builddir
> +++ b/scripts/oe-setup-builddir
> @@ -64,6 +64,7 @@ if [ -n "$TEMPLATECONF" ]; then
> fi
> OECORELAYERCONF="$TEMPLATECONF/bblayers.conf.sample"
> OECORELOCALCONF="$TEMPLATECONF/local.conf.sample"
> + OECORESITECONF="$TEMPLATECONF/site.conf.sample"
> OECORENOTESCONF="$TEMPLATECONF/conf-notes.txt"
> fi
>
> @@ -77,9 +78,11 @@ You had no conf/local.conf file. This configuration
> file has therefore been
> created for you with some default values. You may wish to edit it to, for
> example, select a different MACHINE (target hardware). See conf/local.conf
> for more information as common configuration options are commented.
> -
> +Also check conf/site.conf for site specific settings such as proxies and
> +download cache locations.
> EOM
> cp -f "$OECORELOCALCONF" "$BUILDDIR/conf/local.conf"
> + cp -f "$OECORESITECONF" "$BUILDDIR/conf/site.conf" || true
> SHOWYPDOC=yes
> fi
>
> @@ -107,6 +110,7 @@ fi
> # Prevent disturbing a new GIT clone in same console
> unset OECORELOCALCONF
> unset OECORELAYERCONF
> +unset OECORESITECONF
>
> # Ending the first-time run message. Show the YP Documentation banner.
> if [ ! -z "$SHOWYPDOC" ]; then
> --
> 2.30.2
While I can't speak for others, this change will break our build environment.
We have a global site.conf file in an NFS directory that everyone use. It
contains all proxy settings and similar that are required to build inside the
corporate environment. Copying a dummy site.conf file into the local build
directory will prevent the global file from being used.
//Peter
next prev parent reply other threads:[~2022-07-07 13:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-06 18:23 [PATCH 1/2] scripts/oe-setup-builddir: copy site.conf.sample out of template directories (if it exists) Alexander Kanavin
2022-07-06 18:23 ` [PATCH 2/2] bitbake-layers: add a command to save the active build configuration as a template into a layer Alexander Kanavin
2022-07-07 13:26 ` Peter Kjellerstedt [this message]
2022-07-07 13:36 ` [OE-core] [PATCH 1/2] scripts/oe-setup-builddir: copy site.conf.sample out of template directories (if it exists) Alexander Kanavin
2022-07-07 13:45 ` Peter Kjellerstedt
2022-07-07 13:56 ` Alexander Kanavin
2022-07-07 14:38 ` Peter Kjellerstedt
2022-07-07 14:48 ` Alexander Kanavin
2022-07-07 15:21 ` Peter Kjellerstedt
2022-07-15 14:42 ` Richard Purdie
2022-07-15 16:00 ` Alexander Kanavin
2022-07-15 21:57 ` Alexandre Belloni
2022-07-16 7:37 ` Alexander Kanavin
2022-07-15 16:15 ` Alexander Kanavin
2022-07-15 16:24 ` Richard Purdie
2022-07-15 16:35 ` Alexander Kanavin
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=d04fa3ca7398489a99f8356b17f1174a@axis.com \
--to=peter.kjellerstedt@axis.com \
--cc=alex.kanavin@gmail.com \
--cc=alex@linutronix.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox