Split out GVDB as a separate library
Currently, the canonical location for the GVDB code is here in GLib, but copies are used in dconf and other projects. Its old canonical location was a separate repository, but that was (deliberately or accidentally) archived when we moved to GitLab.
Let’s take this opportunity to work out the best way for GVDB to be maintained and used in future. Having copies in multiple source trees, either using git submodule
or git merge
seems suboptimal, even if the code doesn’t change much. We should either merge it into GLib properly, as a public API; or split it out as a separate library which can be installed and used system wide as appropriate. (Or, if people don’t want the slight overhead of linking to another library, they can use it as a meson subproject, and statically link to it.)