Hello Chuck,
On Mon, 16 Jan 2023 17:59:30 -0800
"Chuck Wolber" <chuck.wol...@boeing.com> wrote:
> The effect of subsequent setup-layers executions is now either a NOOP
> or the minimal set of changes required to ensure layers precisely match
> the JSON configuration.
>
> This change allows setup-layers to be incorporated into a team's
> configuration management strategy. In particular, the configuration
> JSON manages a "pinning policy" that documents the oversight of sources
> of change (a requirement for embedded development in highly regulated
> industries).
>
> One model for this strategy would work as follows. Team level policy is
> developed to regularly review upstream commits that occur between the
> current upstream HEAD and the previously pinned revision. The JSON
> configuration is periodically updated after a review, test, and approval
> process. In the rare instance that an upstream change is considered
> problematic, the bbappend mechanism can be used to make relevant
> changes in the team's project repository. This approach also requires
> that team developers regularly run the project repository copy of
> setup-layers. This is most easily accomplished by including setup-layers
> in a wrapper script that all team developers use to interact with the
> bitbake tool suite (e.g. "bb bitbake foo-image"). Project level policy
> and oversight is effectively "contained" within this wrapper script,
> thereby reducing a significant source of human error.
>
> Left unstated, but acknowledged here, are a number of nuances required
> to successfully implement the above strategy. The details are out of
> scope for this explanation. What should be clear is that a larger
> configuration management strategy can now benefit from the utility
> provided by setup-layers.
>
> Note: Neither the above configuration management strategy example nor
> the change itself is intended to alter the original intent to use
> "bitbake-layers create-layers-setup destdir" to keep pace with upstream
> activity for those who wish to use it that way.
>
> Signed-off-by: Chuck Wolber <chuck.wol...@boeing.com>
I'm afraind I am unable to apply this patch on my testing branch as it
conflicts with another patch ("oe-setup-build: add a tool for
discovering config templates and setting up builds" by Alexander
Kanavin) which is already on my branch.
You might want to rework your patch on top of Alex's, or just wait for
it to be on master and then send a v3.
Kind regards,
Luca
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#176056):
https://lists.openembedded.org/g/openembedded-core/message/176056
Mute This Topic: https://lists.openembedded.org/mt/96322236/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
