-
-
Notifications
You must be signed in to change notification settings - Fork 185
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add FFmpeg 5.0 #96
Comments
What needs to be done from the
|
I am currently waiting on patches for FreeBSD to show up in ports :( pending commit: |
@Thefrank any news? 🙂 |
It still has not even made it to FreeBSD ports. Sorry about all of the delays here! |
Maybe this is better, why don't release FFmpeg 5.0? When user is using FreeBSD, then download FFmpeg 4.4 instead. |
As an added thought here, would you be open to an MR (or this may require a fork) that implements this logic:
This would allow users to lock in the specific versions of ffmpeg that they require. |
@tylerssn That already is a feature of all common package managers, right? There is a not very detailed doc for Yarn and one for npm on this. Or am I misunderstand you? |
@wolf-yuan-6115 @Thefrank I'll remove FreeBSD in |
For FreeBSD, currently there are no ffmpeg 5.0 binaries available. See #96
Published as |
Of course 😺 . I was just proposing two options to go about it—use the normal semantic versioning, except the major number represents the FFmpeg version. Or to use semantic versioning for the repository ( Either way, thanks for the quick work on this! |
How would I upgrade the required Node.js version then, which is a breaking change, if no major ffmpeg version has been published?
But then all the built-in SemVer mechanisms don't work anymore (e.g. |
Looking at the dist tag docs, I don't think those will do the trick either. Going back to what you actually implemented, that may be the win since this repo is literally Thanks much for the work on this. |
5.1.6ffmpeg
ffprobe
|
FFmpeg 5.0 is released now, but
ffmpeg-static
doesn't update yet.These mirrors have FFmpeg 5.0:
These mirrors don't have FFmpeg 5.0:
Platforms already have FFmpeg 5.0 binaries:
Platforms don't have FFmpeg 5.0 binaries:
The text was updated successfully, but these errors were encountered: