[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#886322: libkf5kdelibs4support-dev: Should libkf5kdelibs4support-dev still depend on libssl1.0-dev



On 01/04/2018 02:25 PM, Pino Toscano wrote:
On giovedì 4 gennaio 2018 14:17:59 CET Eric Valette wrote:
this is a duplicate of bug #850888, since the dependency in the -dev
package depends on which libssl was used for the build.  When
kdelibs4support is ported to libssl1.1, then the dependency in the -dev
package will be updated.
But if the kdelibs4supportpackage was build using libsll1.0-dev, then
some  kdelibs4support generated packages should depend on libsll1.0.0
which is not the case.

kdelibs4support is built against libssl1.0.  There are few publich
headers of it that include libssl headers, so that warrants the
dependency in the -dev package -- but they are not used a lot, so it
will not cause a dependency on that on the majority (if not all) of
packages that build using kdelibs4support (also almost all the
kde-related packages are built using --as-needed).

So, what you said is not true, and partially does not make any sense.

Sorry to be stupid but:

If I understand, the include exported libkf5kdelibs4support-dev by require the sll headers because some of them are included but are not used by the packages itself. Right?

But then other packages build using kdelibs4supportpackage-dev should then depend on libsll1.0.0 if they really use the headers requiring ssl includes and sll API and not only macros which is not the case as shown via apt-rdepends in original report.

So I still wonder if this should be libsll1.0-dev or libssl-dev. And in any case this should be reworked for the ssl 1.1 transition as mentioned already. Nevermind

-- eric


Reply to: