All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: Mikko Rapeli <mikko.rapeli@linaro.org>,
	Richard Purdie <rpurdie@rpsys.net>
Cc: Ross Burton <ross.burton@arm.com>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: RE: [OE-core] [PATCH 1/2] poky.conf: allow changes to DISTRO_VERSION, SDK_VERSION and MAINTAINER
Date: Thu, 22 Sep 2022 13:55:51 +0000	[thread overview]
Message-ID: <d4ddb00322c14cee9580c16e0c786f3e@axis.com> (raw)
In-Reply-To: <CAJFpGrPS+uuihkS0+E0+gPoPFB8wRNEsLZSgVWG_zR4C8EeNiQ@mail.gmail.com>

> -----Original Message-----
> From: openembedded-core@lists.openembedded.org <openembedded-
> core@lists.openembedded.org> On Behalf Of Mikko Rapeli
> Sent: den 22 september 2022 15:44
> To: Richard Purdie <rpurdie@rpsys.net>
> Cc: Ross Burton <ross.burton@arm.com>; openembedded-
> core@lists.openembedded.org
> Subject: Re: [OE-core] [PATCH 1/2] poky.conf: allow changes to
> DISTRO_VERSION, SDK_VERSION and MAINTAINER
> 
> Hi,
> 
> Thanks for the feedback. My product isn't a real one, it's actually
> some meta layers to be used
> by others to create real products.
> 
> The reason for using poky.conf distro is to stay as close to it as
> possible. But I still need to know
> what is the output of my builds vs. something else from poky.
> 
> If chaning these veriables from local.conf is bad practice, then I
> need to find other possibilities, like
> the custom distro config (maybe move away from kas). But the aim is to
> do as few changes to
> poky as possible.
> 
> Cheers,
> 
> -Mikko
> Cheers,
> -Mikko

If all you want is for your values from your local.conf to be used, 
then you can use an override when setting the variables. In this 
case, since you want to override the values from the poky distro, 
why not use it as the override, e.g.:

DISTRO_VERSION:poky = "my-version"

//Peter


      reply	other threads:[~2022-09-22 13:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-22 12:24 [PATCH 1/2] poky.conf: allow changes to DISTRO_VERSION, SDK_VERSION and MAINTAINER Mikko Rapeli
2022-09-22 12:24 ` [PATCH 2/2] git-describe.bbclass: add new class for "git describe --tags --allways --dirty" Mikko Rapeli
2022-09-22 12:43   ` [OE-core] " Ross Burton
2022-09-22 13:16   ` Martin Jansa
2022-09-22 12:30 ` [OE-core] [PATCH 1/2] poky.conf: allow changes to DISTRO_VERSION, SDK_VERSION and MAINTAINER Alexander Kanavin
2022-09-22 12:42 ` Ross Burton
2022-09-22 12:45   ` Richard Purdie
2022-09-22 13:43     ` Mikko Rapeli
2022-09-22 13:55       ` Peter Kjellerstedt [this message]

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=d4ddb00322c14cee9580c16e0c786f3e@axis.com \
    --to=peter.kjellerstedt@axis.com \
    --cc=mikko.rapeli@linaro.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@arm.com \
    --cc=rpurdie@rpsys.net \
    /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.