New comment by q66 on void-packages repository

https://github.com/void-linux/void-packages/pull/17766#issuecomment-576305583

Comment:
Debian:

https://packages.debian.org/sid/alpha/libgladeui-2-6/filelist
https://packages.debian.org/sid/libgladeui-2-6

all the modules are in `libgladeui` and it depends on both Python and Webkit.

The data files are then present in `libgladeui-common`, I don't think we need to split as much as that.

Since both the python and webkit modules appear to be optional, here is what we could do:

1) Move the modules and appropriate data in `libgladeui3`
2) Create `libgladeui3-python` and `libgladeui3-webkit`, each depending on `libgladeui3`; afterwards, the applications that require those modules could depend on them explicitly (there doesn't seem to be any of those, though)

I'd disregard whatever Arch does, they always do things strange and not always correctly.