The packagegroups of sdv recipes are not properly separated yet.
In this PR, i give a proposal on how to separate the packagegroups to make them more easy to reuse for specific images:
Core: minimum set of core system components to run the SDV.EDGE stack, eg container runtime, mosquitto, rauc etc
Additions: additional components to ease additional use cases, eg ssh server, openvpn, alternative container runtime
Examples: example applications such as the seat service
Tools: Convenient tools for developing and troubleshooting
Rescue: Tools for implementing a rescue use case ("Reset Device to Factory Settings")
Except for the "Core" packagegroup, all other components are supposed to be optional.
The Core packagegroup must only contain the absolute minimum to get the edge stack up and running.
Otherwise, the reusability of the metalayer is at risk.
The packagegroups of sdv recipes are not properly separated yet.
In this PR, i give a proposal on how to separate the packagegroups to make them more easy to reuse for specific images:
Except for the "Core" packagegroup, all other components are supposed to be optional. The Core packagegroup must only contain the absolute minimum to get the edge stack up and running. Otherwise, the reusability of the metalayer is at risk.