Hello, On trečiadienis 04 Gegužė 2011 19:23:53 Kurt Roeckx wrote: > On Wed, May 04, 2011 at 01:15:18PM +0300, Modestas Vainius wrote: > > Hello, > > > > On antradienis 26 Balandis 2011 20:47:45 Thorvald Natvig wrote: > > > That being said, Qt also supports explicit compile-time linking to > > > libssl and libcrypto, which avoids issues like this one and also > > > ensures that libqt4-network shows up as a reverse dependency for > > > openssl. If nothing else, the runtime libraries for OpenSSL should be > > > added as a recommends: for the libqt4-network package. But in todays > > > crypto-heavy world, I can't really think of a good reason not to just > > > link it. Among other things, Qt's web widgets (and URL classes) will > > > not support https without libssl/libcrypto. > > > > OpenSSL license is THE reason. Or pure-GPL apps won't be able to link > > against libQtNetwork which is unacceptable. > > I think dynamicly loading instead of linking doesn't change this > license problem. Well, at least openssl is not always loaded, but on demand. GPL app may not ever use SSL and so openssl won't ever be in the same process space. While there are multiple views on this kind of issues, you should agree that explicit linking is worse. -- Modestas Vainius <modax@debian.org>
Attachment:
signature.asc
Description: This is a digitally signed message part.