chromium disabling use of shared libs, BoringSSL

[Daniel Pocock <daniel@pocock.pro>]

Chromium upstream are keen to discourage use of shared libraries on the
system and encourage packagers to bundle their own versions.

This has been discussed in the context of libsrtp[1] but I can imagine
them using the same approach for other things in Chromium.

Has anybody else come across these situations with Chromium or Google
developers or other projects using BoringSSL?

Will the security team be happy to continue supporting the package?

Regards,

Daniel


1. https://code.google.com/p/chromium/issues/detail?id=501318