One problem is it needs to try to switch to using json-glib and jsonrpc-glib as dependency packages not included source code.
The reason is that there's this performance problem
https://gitlab.gnome.org/GNOME/json-glib/-/merge_requests/60
which got only fixed in the latest 1.10 release which was released 1 month ago and probably isn't part of many distributions yet. I was hoping to use the bundled version until the latest dependencies get to more distros.
Since the performance problem only affects semantic tokens as far as I know (but now thinking about it, it could also be document symbols for the symbol tree), one possibility would be to ifdef-out semantic token support for older json-glib versions.
I will note some distros (I suspect Debian for eg) will require that or they might not add the plugin due to the included source.
Is there some policy preventing this? Couldn't I just claim these are the sources of the plugin? Scintilla and ctags are also bundled with Geany (and, well, it's true that Scintilla is supposed to be used this way and there's no official library version of ctags).
Does the build script drop the source code if the dependency packages are available?
There's nothing like that (yet). But would it be OK for Debian to fall back to the bundled version in this case?