On September 25, 2015 11:29:20 AM CDT, "Martin Steghöfer" <mar...@steghoefer.eu> wrote: >Dear kdelibs5-dev maintainers, > >One package I worked on is affected by this problem, too. That's why I >started investigating this issue and found out that there is a whole >bunch of packages that are currently (or were recently) FTBFS'ing >because of this problem. Some maintainers employed the workaround of >adding a build dependency to "libsoprano-dev" because that's the only >way they can fix the FTBFS themselves. But it sure feels like a hack, >which is why I'd prefer not to have to do this. > >What's the reason for this odd behaviour? I couldn't really see this >from this bug report, just that it had something to do with "the >transition from nepomuk to the new baloo package". > >Is this going to be fixed properly at some point? I consider adding >"libsoprano-dev" to the Build-Depends of all dependant packages just a >temporary workaround. > >Could we keep this bug open as a reminder that this still needs a >proper >fix? > >To me it feels really wrong to add a build dependency to a library that > >is never even mentioned in any of the CMakeLists.txt files, nor is used > >directly by any of the code (there is even a warning telling me that I >shouldn't have linked against it). Or is there any justification for >seeing libsoprano-dev as a "real" build dependency of packages of that >kind, and I'm just not seeing it? Or a way to get rid of the >"dependency"?
If there's a warning not to link against it, isn't the solution not to do that? Scott K
