feat: prepare meta-mender-community refactoring #265
Conversation
This reflects 1862576ba943409857986072e19695b73d82ba7a on https://github.com/theyoctojester/meta-mender-community to prepare for the Jetpack4 and Jetpack5 support in meta-mender-community. Changelog: Title Ticket: None Signed-off-by: Josef Holzmayr <jester@theyoctojester.info>
|
@TheYoctoJester thanks for getting this started. Is there a reason to merge this now as opposed to when it's already upstream in meta-mender-community? Typically we've pointed tegra-demo-distro at either the upstream meta-mender-community or our OE4T fork. |
|
@dwalkes no reason at all, just providing the template as proposed on the last call. I'm happy to keep the development in either my branch, or a separate one on meta-mender-community. What I just haven't figured out is how to make the git submodule based approach used by OE4T and the kas based one in meta-mender-community to play nice with each other. |
|
@TheYoctoJester Looking forward on how to solve this problem. I'm trying to use kas too, and the git submodule approach is really annoying to integrate. Thanks for looking at it! |
|
@dwalkes as we're currently sorting out OE4T/meta-mender-community#18, I'll close that one here until the metadata is ready. |
This reflects 1862576ba943409857986072e19695b73d82ba7a on https://github.com/theyoctojester/meta-mender-community to prepare for the Jetpack4 and Jetpack5 support in
meta-mender-community.
Changelog: Title
Ticket: None