Am 31.08.19 um 01:21 schrieb Stefan Brüns:
The automatic dependency only pulls in a specific major version (e.g. libclang.so.8), but binaries often compile in the path to the headers, which contains the full version (e.g. 8.0.1). A method to retrieve the path to the header files is only provided starting with with LLVM 9.
I know, but it's a well known problem and there are solutions to that. (e.g. https://phabricator.kde.org/D15955 in KDevelop) Admittedly it's not ideal and Clang should have named their builtin header directory like GCC does, but I guess the ship has sailed on that. It might be a leftover from the times when Clang still had minor versions != 0. I'd be curious to know about the change in LLVM 9 that makes this easier because it doesn't seem to be mentioned in the release notes. Perhaps it should be mentioned there.
On the other hand, both libqt5-qttools and libqt-qttools-doc should not be pulled in by the devel package, as the binary tools are not required when linking to the libraries. Especially as qdoc pulls in quite some more packages. That's quite possible. My thinking was that maybe qttools-doc uses libclang to generate some kind of documentation from C++ source code, and could thus be required for developers, but maybe that isn't it. The devel package covers all parts of libqt5-qttools, but most packages only need the headers and libraries for compiling and linking. QDoc is only required to generate HTML help files from inline source documentation.
If libqt-qttools[-doc] contain no libraries needed by the -devel package, then maybe the package name is misleading? I guess there is some reason for this naming scheme, but we have this convention that libX-devel should depend on libX for all X. Best regards, Aaron -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org