Meida/WebRTC/libsrtp Update Process: Difference between revisions
Jump to navigation
Jump to search
(Adding instructions for the libsrtp update process) |
(Adding updatebot info) |
||
| Line 9: | Line 9: | ||
# Make any changes necessary to accommodate build changes | # Make any changes necessary to accommodate build changes | ||
# Commit the new version | # Commit the new version | ||
==== Moving to updatebot ==== | |||
It may be possible to use [https://github.com/mozilla-services/updatebot mozilla-services/updatebot] to keep libsrtp up to date. There is a bug to support this from the updatebot side [https://github.com/mozilla-services/updatebot/issues/230 here]. | |||
Revision as of 01:56, 9 February 2022
The main repository for libsrtp is maintained by Cisco and hosted on GitHub: https://github.com/cisco/libsrtp. It is vendored into our tree inside third_party/libsrtp/src. Inside of the parent directory there is a log of the updates in srtp_update.log and an update helper script update_srtp.sh.
Steps to update the repository:
- Checkout the desired release of libsrtp from GitHub
- Revert any existing patches (if any) that we have applied on top of the current vendored version
- Follow the instructions inside of the update script to vendor a new version
- Reapply the patches reverted in step one
- Make any changes necessary to accommodate build changes
- Commit the new version
Moving to updatebot
It may be possible to use mozilla-services/updatebot to keep libsrtp up to date. There is a bug to support this from the updatebot side here.