[RFE] Validate SL Micro versions

[e-minguez]

Currently EIB doesn't enforce any SL Micro version (which is ok), but things like using EIB 1.1 with SL Micro 6.1 can lead to issues (like #632).

It would be nice to show a warning when the OS version and EIB version don't match.

[hardys]

Showing a warning by default would be good, but we should consider adding a build time flag perhaps so that the warning can become an error for downstream builds, so we can more easily ensure only supported combinations are used for customer/production use-cases.

[e-minguez]

Showing a warning by default would be good, but we should consider adding a build time flag perhaps so that the warning can become an error for downstream builds, so we can more easily ensure only supported combinations are used for customer/production use-cases.

That would be even better, agree

[jomeier]

I would like to throw in an extension of that idea:

Would it be possible that users can provide own "pre installation gate" scripts that check if an installation is possible or not?

Use Case:
Only certain versions of an installation or update might be spupported by the business domain or target edge environment. For example: If a costumer tries to install version A on an edge environment that already has Version C installed, this could end in an unsupported downgrade of the software stack.

This scenario could be supported by custom installation scripts provided by edge image builder users/developers that check all preconditions before installation and show use case specific dialogs BEFORE a new version of the OS is 'dded' to the disk.

In my opinion that script based "pre installation gates" are use case specific and cannot be generalized.