Bug#866784: libsrtp2-dev: Missing includes

Sandro Knauß hefee at debian.org
Sat Jul 1 19:34:47 UTC 2017


Hey Jonas,

> I am quite in favor of getting rid of code copies, but using on a
> private library sounds like abuse which should be solved by either
> rewriting/patching the project to only use public headers, or convince
> the libsrtp project to make those private headers public.

Well qtwebengine is a embeded browser (chromium) and needs the private headers 
to build webrtc. Keep in mind also chromium is normally affected by issues, 
that are stopping qtwebengine to use system packages (see as example #812091).

We had no issue to use system libsrtp-dev, because this had shipped the 
private header.

I know shipping private header stuff is not ideal. But I prefer no copies and 
one more transition if private stuff changes. Sorry but I have nor real indeep 
knowlege, why webrtc needs the private stuff. I hope the surroundings are 
enough to start the discussion with upstream.

Btw. upstream(qt) tells actually that qtwebengine using an non released 
version of libsrtp (https://bugreports.qt.io/browse/QTBUG-60970)

> I can forward this issue to the upstream developers of libsrtp, but will
> then need some more substantial arguments why headers deliberately made
> private should be made public. Even better if you get in touch with
> upstream directly, as you can no doubt explain your needs better than me
> acting as proxy.

As I don't know libsrtp it may be better if you start the discussion. I can 
join afterwards. Otherwise you should discribe me, how to reach them properly.

Best Regards,

sandro
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.alioth.debian.org/pipermail/pkg-voip-maintainers/attachments/20170701/1c1c02d0/attachment.sig>


More information about the Pkg-voip-maintainers mailing list