On Wed, 12 Jul 2023 at 23:53, Chuck Wolber <[email protected]> wrote: > But this is why I chose not to. By definition the setup-layers concept allows > for a project specific repository to > manage change, including change in openembedded-core. The same would go for > update-layers. If we folded > update-layers into bitbake-layers, you get a chicken/egg problem so it made > more sense (in my mind) to treat > update-layers like setup-layers - have it dropped in by bitbake-layers when > it drops in setup-layers. > > But your question exposes a missing feature in update-layers - it should do a > final check for an updated setup-layers > and update-layers script and inform the user that the project distro > repository needs to have those scripts updated > as well. > > If my reasoning makes sense, I can put the time and energy into a set of > OE-Core patches that reflects the > above thinking.
I see setup-layers differently. It's a minimal standalone script that is meant to do only one thing: set up the layers on local disk as prescribed by content of the json, or bring them in sync with the json. *Everything* else goes into layers where it is managed using standard paths and extension mechanisms (which we can hopefully agree on if they are missing, such as config template locations or additional plugins to create-layers-setup or to bitbake-layers itself, such as, possibly, update-layers plugin). I will resist feature creep in setup-layers or extending create-layers-setup to bundle more files or scripts next to it (originally I wanted to fold json content itself into setup-layers, and only reluctantly agreed to have it as a separate file). If you can describe the chicken/egg problem in greater detail that would be appreciated, because I struggle to understand where it is. The problem can also be approached from a different side: rather than update layer revisions with a separate tool/bitbake-layers extension, why not have create-layers-setup write a json that lists the layer repository and branch, but does not pin it to specific revision, for one or more of the layers? Then setup-layers itself would just sync everything to latest revisions on specified branches when it is run against that json. And if you need to freeze the revisions, then that goes into a second/third/etc. json. Thoughts? Alex
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#184312): https://lists.openembedded.org/g/openembedded-core/message/184312 Mute This Topic: https://lists.openembedded.org/mt/100104869/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
