Moved the -tcp_keepalive ffmpeg option behind a version check (8.1 or higher) - #21
Open
morgant wants to merge 1 commit into
Open
Moved the -tcp_keepalive ffmpeg option behind a version check (8.1 or higher)#21morgant wants to merge 1 commit into
morgant wants to merge 1 commit into
Conversation
…as introduced in ffmpeg 8.1 (available in -current, but not 7.9-stable which has ffmpeg 8.0.3). Issue rfht#20
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
As discovered & reported in issue #20, the
-tcp_keepaliveffmpeg option was introduced in ffmpeg 8.1 (available in -current, but not 7.9-stable which has ffmpeg 8.0.3). This moves its use behind a version check.Even when OpenBSD 8.0 is released, 7.9 will still be officially supported for security patches, so it's probably best to preserve this version check until then. It may be best to leave the ffmpeg version determination anyway, as there may be future options/functionality that could/need to be guarded behind checks.