From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>,
Alexander Kanavin <alex@linutronix.de>,
Richard Purdie <richard.purdie@linuxfoundation.org>
Subject: RE: [OE-core] [PATCH 2/2] scripts/oe-setup-builddir: add a check that TEMPLATECONF is valid
Date: Thu, 25 Aug 2022 19:41:45 +0000 [thread overview]
Message-ID: <93d7371f57bb44ae96a55d5349982bc6@axis.com> (raw)
In-Reply-To: <CANNYZj94cymsa-TmkcMmHWm2FQ6CvRvKE3_eCy=t63x9NFZnhA@mail.gmail.com>
> -----Original Message-----
> From: Alexander Kanavin <alex.kanavin@gmail.com>
> Sent: den 25 augusti 2022 11:19
> To: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
> Cc: openembedded-core@lists.openembedded.org; Alexander Kanavin
> <alex@linutronix.de>; Richard Purdie <richard.purdie@linuxfoundation.org>
> Subject: Re: [OE-core] [PATCH 2/2] scripts/oe-setup-builddir: add a check
> that TEMPLATECONF is valid
>
> On Thu, 25 Aug 2022 at 09:19, Peter Kjellerstedt
> <peter.kjellerstedt@axis.com> wrote:
> >
> > > We are trying to move towards standardizing build configuration
> > > management. One step towards that goal is that config templates must
> > > live in meta-some-layer/conf/templates, and aren't scattered around,
> > > or generated on the fly. This rule only makes sense if there is some
> > > way to enforce it, which is what this change does.
> >
> > Well, we gave up on the static templates almost immediately after we
> > started using Yocto when we realized that they did not fit into our
> > idea of being able to mix layers in different combinations in different
> > builds. We rely on repo fetching the layers that are supposed to be part
> > of the build, and then we generate a bblayers.conf.sample that matches
> > the fetched layers.
>
> The static templates is only a starting point. The next step would be
> to support prefabricated 'configuration fragments' stored inside
> layers that can be dynamically added/removed into local.conf and/or a
> distro definition, so ideas for the design and UI would be welcome.
Well, the way we have solved that is to allow a layer to contain
conf/local.conf.sample.XX files (and also conf/conf-notes.txt.XX files)
where XX is any number between 00 and 99. We also assume the sample
files from meta-poky have XX == 50. Then when we generate our
templateconf directory, we concatenate all these files ordered by XX
(regardless of which layer they come from).
>
> Alex
//Peter
next prev parent reply other threads:[~2022-08-25 19:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-24 12:42 [PATCH 1/2] meta/conf: move default configuration templates into meta/conf/templates/default Alexander Kanavin
2022-08-24 12:42 ` [PATCH 2/2] scripts/oe-setup-builddir: add a check that TEMPLATECONF is valid Alexander Kanavin
2022-08-24 13:58 ` [OE-core] " Peter Kjellerstedt
2022-08-24 14:08 ` Alexander Kanavin
2022-08-24 14:43 ` Peter Kjellerstedt
2022-08-24 14:52 ` Alexander Kanavin
2022-08-25 7:19 ` Peter Kjellerstedt
2022-08-25 9:19 ` Alexander Kanavin
2022-08-25 19:41 ` Peter Kjellerstedt [this message]
2022-08-27 7:00 ` Luca Ceresoli
2022-08-27 17:00 ` Alexander Kanavin
[not found] ` <170F423CB671B42F.16609@lists.openembedded.org>
2022-08-27 19:13 ` Alexander Kanavin
2022-08-25 13:37 ` [OE-core] [PATCH 1/2] meta/conf: move default configuration templates into meta/conf/templates/default Luca Ceresoli
2022-08-25 13:45 ` Alexander Kanavin
2022-08-26 9:04 ` Luca Ceresoli
2022-08-26 9:08 ` Alexander Kanavin
2022-08-26 10:27 ` Luca Ceresoli
2022-08-26 10:46 ` 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=93d7371f57bb44ae96a55d5349982bc6@axis.com \
--to=peter.kjellerstedt@axis.com \
--cc=alex.kanavin@gmail.com \
--cc=alex@linutronix.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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.