core-deps/libsigcplusplus-2.0: Shall mm-common be a build-dependency?
mm-common is listed as a dependency of core-deps/libsigcplusplus-2.0.bst.
build-depends:
- freedesktop-sdk.bst:components/m4.bst
- freedesktop-sdk.bst:public-stacks/buildsystem-meson.bst
depends:
- core-deps/mm-common.bst
- freedesktop-sdk.bst:bootstrap-import.bst
It's needed when libsigcplusplus-2.0 is built. It's not needed when code in the built library file is executed. Then it can be listed as a build-dependency, I suppose.
build-depends:
- freedesktop-sdk.bst:components/m4.bst
- freedesktop-sdk.bst:public-stacks/buildsystem-meson.bst
- core-deps/mm-common.bst
depends:
- freedesktop-sdk.bst:bootstrap-import.bst
If it's only a build-dependency of libsigcplusplus-2.0, mm-common must be listed as a build-dependency also in several modules that depend on libsigcplusplus-2.0, directly or indirectly. Many modules depend indirectly on libsigcplusplus-2.0 via glibmm-2.4 and NetworkManager. I know nothing about NetworkManager and the modules that depend on it. It may take some time to find out which modules need mm-common as a build-dependency. Might even any module need mm-common at run-time? Unlikely.
Is it worth the trouble to fix this?