@neo:
You don't really have to explain this nonsense to me .
If there is an Enigma2 built on the OE 2.5 or OE 2.6 core, then I know that it is a Dreambox, the new original version of the E2 core.
And if I write that E2 is built on the basis of the OE 1.6 or 2.0 core, as a developer it is clear to me that this is the classic open source Enigma2 GUI version of the core.
And then I know how to build my plugin . It is clear to me that whether it is Enigma2 built on the old core or on the Dreambox core. As a plugin developer, I need to be able to differentiate between core-based Enigma 1.6, 2.0, 2.3, 2.5, 2.6+, etc. ...... but as a developer, I may not be interested in anything more . You know ? The plugin must work always and everywhere.
If there are other, specific E2 cores, which are also completely different from the "standard" E2 core (the one based on 2.0), where their own rules are formed (like in VTi, for example), then this is just useless and another chaos. I usually ignore it or I prefer to delete the function from the plugin source code completely so that the plugin works correctly in every Enigma2 distribution.
The fact that the creators of the open source Enigma2 came up with their own labeling of the Enigma2 core is of no interest to me personally. The changes are very small and unfortunately do not copy the changes at all (such as from the original OE 2.6 from Dreambox). If compatibility is not maintained, compatibility and universality problems arise when using many plugins (xxxxxx_all).
From my perspective as a developer, I know that Enigma2 / OpenPLi, for example, is built on the basis of OE 2.0. And that's what I need to know.
If Enigma2 OpenPLi was built on the basis of the OE 2.6 core (OE 2.6 compatibility), then I would not have to modify the plugin so that it works separately in each Enigma2.
This is indeed the case, namely that the Enigma2 open source development teams already use their own, new, superior version numbering (4.4 for example) and even new "based" cores, as copied coress from other developers. This creates incredible chaos in the world of Enigma2.
Of course, in the case of OE 2.0, it is an always updated and newer core than the ancient 2.0 (which existed years ago and was maintained by Dreambox). Even if the Enigma2 development teams label it differently, for me it is important that it is an Enigma built on the basis of OE 2.0.
Similar opinion also exists in the OS-Windows world. Kernels like 95/98/98SE were virtually identical. The same was true for NT/2000/XP versions, for example. And then came the new kernel of Windows 7/8/8.1/10/11 systems where the kernels are also almost identical. I don't care about code names, I don't care about "what's new", etc. . As a programmer, I was only interested in the fact that it was not even necessary to rewrite the system driver under one compatible kernel... just a few lines and it was done. However, when you wanted to change the system driver intended for Win-98, for example, and transfer it to Win-10, it was an incredibly big problem. Therefore, for me, as a programmer, it is important to know how to distinguish kernels, as a developer. And not like Wikipedia ;-).
If you have a detailed list of all changes related to the Enigma2 GUI core by version or by some builds or something... please show it to me. I will be happy if I know concretely all the changes in E2 versions of different builds from different development teams. I will be able to maintain compatibility in the plugin. Thank you in advance.