Comment 11 for bug 1497945

I don't think this should be too difficult to solve.
For Windows and macOS, this virtually a non-issue, as a single software version is usuall bundled together on these platforms.

On Linux and other Unix-like operating systems, it should be sufficient to tie a plugin to a certain KiCad release version. The main program should then use a library path such as /usr/lib/kicad/5.0 - with a fallback to /usr/lib/kicad if no plugin can be found.

If one wants to get fancy, the host triplet could be added as well (like in /usr/lib/i386-linux-gnu/kicad/), but that is rarely useful.