Lisandro Damián Nicanor Pérez Meyer: > On Tuesday 22 March 2016 03:48:48 Chris Knadle wrote: [...] >> Lisandro Damián Nicanor Pérez Meyer: >>> Actually the binary built can be installed in a private path alongside >>> qtnetwork (in it's package) and might even be a private lib without >>> headers. That should be enough to keep stuff in sync. >> >> I'm not sure I fully understand this, but it vaguely sounds good. > > Easy: instead of creating a new package just ship a very very simple app > alongside libqt4-network/libqt5network5. This will make dh_shlibdeps add the > current version of libssl as a dependency of the package so we can warrant > two > things: the src package will get rebuilt with any libssl transition and an > appropriate version of libssl will be a hard dependency of each qtnetwork > package. > > We just need to use the proper licensing for that dummy app :) > > That being said I'm not having much time on my hands to code and integrate > the > app, although I would definitely do it if I happen to have it.
If you have an idea of what you'd like the result to look like, that would at least give me an idea I might be able to work with. [I might be able to make time to try to build something if I know what it needs to be.] >>> By the way, how is mumble's porting to qt5 going? >> >> That part is already ready. Mumble 1.3.x (which doesn't yet have a release) >> already builds with Qt5 fine and I've got the Debian packaging ready for >> when there's a release to ship. Mumble 1.3.x can be built with Qt4 or Qt5, >> Mumble 1.4.x will be Qt5 only. > > Excellent! Let's hope that happens in time for Stretch. It should. There's a somewhat pressing need for Mumble 1.3.x because Qt5 is needed in order to support Perfect Forward Secrecy. AFAIK the earliest Stretch freeze is November 5th and there have been a number of 1.3.x snapshots, so it seems like a release is close. -- Chris Knadle chris.kna...@coredump.us
