Initial scarthgap compatibility

[hikinggrass]

Minimal changes to get scarthgap compatibility on the kirkstone branch. Since there are no major changes needed I just added this to the kirkstone branch to not have 2 almost identical branches that need to be kept up2date with each EVerest update

[mhei]

Sorry, but personally I disaggree with the proposed approach. Even if there are no marjor changes now, I'd prefer to have the workflow established.

First, I would like to extend the README in this repo here to document, how the EVerest community supports different Yocto releases/branches. I can work on this but due to starting holidays, I cannot make any promises.

In addition to this organizational comment, some technical notes:

• Some recipes (mostly the backported ones) are obsolete with scarthgap, since already included and even available in a newer version. This is why I'd recommend to drop them here.
• This is why I also would prefer to have a dedicated branch for each (Yocto) upstream release.
• I encountered build problems with the OCPP 2.0.1 module with the C++ compiler version in scarthgap but since I tried to build for our Tarragon platform and had to fiddle a little bit around to push it through, I'm not yet sure that I messed things up on my side. I'll investigate.

Disclaimer: personal opinion, not discussed/consolidated with with my employer team

[hikinggrass]

Sorry, but personally I disaggree with the proposed approach. Even if there are no marjor changes now, I'd prefer to have the workflow established.

First, I would like to extend the README in this repo here to document, how the EVerest community supports different Yocto releases/branches. I can work on this but due to starting holidays, I cannot make any promises.

In addition to this organizational comment, some technical notes:

• Some recipes (mostly the backported ones) are obsolete with scarthgap, since already included and even available in a newer version. This is why I'd recommend to drop them here.
• This is why I also would prefer to have a dedicated branch for each (Yocto) upstream release.
• I encountered build problems with the OCPP 2.0.1 module with the C++ compiler version in scarthgap but since I tried to build for our Tarragon platform and had to fiddle a little bit around to push it through, I'm not yet sure that I messed things up on my side. I'll investigate.

Disclaimer: personal opinion, not discussed/consolidated with with my employer team

I agree, let's have different branches for kirkstone and scarthgap, this was pretty much just a quick poc to see how much is needed to get this to work 😄