make example image package selections reusable

[fmoessbauer]

This patch carves out the package selections from the example image. The selections provide great value for downstream users that do not want to base their image on the example image, but still want to avoid re-creating these selections to e.g. make wifi work.

Signed-off-by: Felix Moessbauer felix.moessbauer@siemens.com

[fmoessbauer]

@BaochengSu : I'll keep you as the author of the package-selections file, as my only contribution was to copy the content.

[jan-kiszka]

I vaguely recall a proposal by @AsuraZeng to have a more fine-grained feature selection, also via Kconfig. Don't find this anymore, but this here should be aligned while we are refactoring.

[AsuraZeng]

I vaguely recall a proposal by @AsuraZeng to have a more fine-grained feature selection, also via Kconfig. Don't find this anymore, but this here should be aligned while we are refactoring.

yes, my proposal at the time was to exclude the necessary software, divide other software according to function blocks and those could be selected through kconfig.

[fmoessbauer]

Independent of the feature-selection concept, I still believe that this patch is valuable. Especially for downstream users it is much easier to use the provided variables directly. Also things like inspection and removal from these vars is possible, which is hard to achieve with a pure feature-selection based approach.

In short, we don't want to use the example image, but still do want to use pre-selected packages for the wifi.

[jan-kiszka]

If there is no overlap or immediate conflict with the feature selection (as I said, I didn't find the changes anymore), then I'm fine with this step.

[fmoessbauer]

@AsuraZeng any news on this topic? Is there something missing from my side?