Openembedded Core Discussions
 help / color / mirror / Atom feed
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/6] scripts/oe-setup-builddir: make it known where configurations come from
Date: Fri, 29 Jul 2022 19:55:08 +0000	[thread overview]
Message-ID: <57a6142f5c2f444288e16632839dc647@axis.com> (raw)
In-Reply-To: <20220729141049.835733-1-alex@linutronix.de>

> -----Original Message-----
> From: openembedded-core@lists.openembedded.org <openembedded-
> core@lists.openembedded.org> On Behalf Of Alexander Kanavin
> Sent: den 29 juli 2022 16:11
> To: openembedded-core@lists.openembedded.org
> Cc: Alexander Kanavin <alex@linutronix.de>
> Subject: [OE-core] [PATCH 1/6] scripts/oe-setup-builddir: make it known
> where configurations come from
> 
> "with some default values" isn't clear; if the user wants to change or
> inspect the default values and their history, we should help them find
> where they are. This becomes especially important when using template
> configs other than poky's.
> 
> Signed-off-by: Alexander Kanavin <alex@linutronix.de>
> ---
>  scripts/oe-setup-builddir | 11 ++++++-----
>  1 file changed, 6 insertions(+), 5 deletions(-)
> 
> diff --git a/scripts/oe-setup-builddir b/scripts/oe-setup-builddir
> index 54048e62ec..b4fec4d120 100755
> --- a/scripts/oe-setup-builddir
> +++ b/scripts/oe-setup-builddir
> @@ -74,9 +74,9 @@ fi
>  if [ ! -r "$BUILDDIR/conf/local.conf" ]; then
>      cat <<EOM
>  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.
> +created for you from $OECORELOCALCONF
> +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.

Please continue to limit the text to within 80 characters (as it was):

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.

or:

You may wish to edit it to, e.g., select a different MACHINE (target hardware).
See conf/local.conf for more information as common configuration options are
commented.

> 
>  EOM
>      cp -f "$OECORELOCALCONF" "$BUILDDIR/conf/local.conf"
> @@ -89,8 +89,9 @@ fi
>  if [ ! -r "$BUILDDIR/conf/bblayers.conf" ]; then
>      cat <<EOM
>  You had no conf/bblayers.conf file. This configuration file has therefore been
> -created for you with some default values. To add additional metadata layers
> -into your configuration please add entries to conf/bblayers.conf.
> +created for you from $OECORELAYERCONF
> +To add additional metadata layers into your configuration please add entries
> +to conf/bblayers.conf.
> 
>  EOM
> 
> --
> 2.30.2

//Peter


  parent reply	other threads:[~2022-07-29 19:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-29 14:10 [PATCH 1/6] scripts/oe-setup-builddir: make it known where configurations come from Alexander Kanavin
2022-07-29 14:10 ` [PATCH 2/6] bitbake-layers: add a command to save the active build configuration as a template into a layer Alexander Kanavin
2022-07-29 14:10 ` [PATCH 3/6] meta/files: add layer setup JSON schema and example Alexander Kanavin
2022-07-29 14:10 ` [PATCH 4/6] bitbake-layers: add ability to save current layer repository configuration into a json file Alexander Kanavin
2022-07-29 14:10 ` [PATCH 5/6] scripts/oe-setup-layers: add a script that restores the layer configuration from " Alexander Kanavin
2022-08-02 13:12   ` [OE-core] " Luca Ceresoli
2022-08-02 14:31     ` Alexander Kanavin
2022-07-29 14:10 ` [PATCH 6/6] selftest/bblayers: add a test for creating a layer setup and using it to restore the layers Alexander Kanavin
2022-08-16 20:29   ` [OE-core] " Richard Purdie
2022-08-16 20:41     ` Alexander Kanavin
2022-07-29 19:55 ` Peter Kjellerstedt [this message]
2022-07-29 20:11   ` [OE-core] [PATCH 1/6] scripts/oe-setup-builddir: make it known where configurations come from Alexander Kanavin
2022-07-30  9:54     ` Peter Kjellerstedt
2022-07-30 17:31       ` Alexander Kanavin
2022-07-30 18:15     ` Chuck Wolber

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=57a6142f5c2f444288e16632839dc647@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