139
edits
Media/WebRTC/libwebrtc Update Process/automation plan: Difference between revisions
Media/WebRTC/libwebrtc Update Process/automation plan (view source)
Revision as of 01:52, 19 October 2022
, 19 October 2022Adding approach
(Adding motivation) |
(Adding approach) |
||
| Line 271: | Line 271: | ||
=== Approach === | === Approach === | ||
We will need to employ several strategies in order to create a robust build environment. | |||
# We will vendor the libraries that libwebrtc requires, but are not provided on our older supported platforms. These dependencies can be kept up to date with `updatebot`. | |||
# We will move vendored shared dependencies from `libwebrtc/third_party` into `third_party`. | |||
As simple as this plan sounds it is complicated by mixed build systems and the current method of importing dependencies into libwebrtc. Eliminating duplicate dependencies also has the risk of running into incompatible version expectations by dependency consumers. | |||
=== Notes === | === Notes === | ||
# (lib)webrtc dependency pinning | # (lib)webrtc dependency pinning | ||