From: zlice <zlice@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: draft: ffmpeg5 split
Date: Fri, 05 May 2023 15:20:44 +0200 [thread overview]
Message-ID: <20230505132044.uqJPGaQyv4jMvM1pxqdMt8d3rBOolRQYP5rjSrXCbVM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42936@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 4202 bytes --]
There's a closed pull request on the void-packages repository
draft: ffmpeg5 split
https://github.com/void-linux/void-packages/pull/42936
Description:
[ci skip]
#### Testing the changes
- I tested the changes in this PR: **YES**
~~I have conflicting changes from [intel packages](https://github.com/void-linux/void-packages/pull/41132) and don't want to mess with my system. If it makes sense I'll move these changes here like I originally intended. ffmpeg5 makes Intel vaapi easier and only rely on oneVPL iirc.~~
I do not use 80%+ of these packages. I may be able to run Blender, and I use shotcut.
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**
#### Local build testing
- I built this PR locally for my native architecture, **x86_64**
#### Discussion
Continuation of https://github.com/void-linux/void-packages/pull/36315 - thx tibequadorian :)
It was suggested to make `ffmpeg` version 5 and 'copy' (create a new?) `ffmpeg4` package, and that seems to work well.
As stated, I haven't and probably won't test most of these packages, hoping for others to voice in on what's working.
A few months back (and now) afaict everything has been compiling with ffmpeg5 except for the few problem packages still using ffmpeg4 (below). Can add to the ffmpeg4 list as a incompatible package is found.
`libavresample` is deprecated, but marked as a dependency when trying to build other packages and install `ffmpeg`(5). I think the right way to handle this is make a meta package and the add to removals?
[gstreamer 1.22.1 updates](https://github.com/void-linux/void-packages/pull/42861) could go before this
##### Commit naming / misc
~~`ffpmeg4` isn't "new", not sure what the commit messages should be really for the 4 and 5 split. Additionally xlint complains about `ffmpeg4` revision being 3 and not 1 because it's a "new" package, I assume that's right but not sure.~~
~~Not sure how commits should be separated. ffmpeg4/5 could be split and all the rev bumps included (otherwise it's over 100 commits). opencv was updated to 4.7.0 for ffmpeg5 so I figured that should be a separate commit?~~
I wouldn't mind moving the [intel packages](https://github.com/void-linux/void-packages/pull/41132) into here under another commit. That just got a potential fix that may allow merging but I imagine moving to ffmpeg5 will change and even remove some of those packages. (I won't really test these changes without Intel vaapi either way.)
Maintainer for previous ffmpeg(4) was orphaned, I can put my name in there if that matters, though I don't exactly see myself keeping up on ffmpeg.
##### STILL FFMPEG4
These are a mix of emulators, games and/or older packages.
- attract (multiple patches in master)
- audacity (3.2.x should work but void is missing some libs? vst3sdk?)
- ccextractor (master patches? no release)
- vice
- mlt
- synfig (mlt)
- tvheadend
- ssr
- spek-alternative
- ppsspp
- olive
- moc
- mediastreamer
- libextractor
- idjc
- hedgewars
- ~~handbrake~~
- ffmpegthumbnailer
- ffmpegthumbs
- deadbeef
- omxplayer
- qtav (fork has ffmpeg 5 patch - https://github.com/cmguo/QtAV)
- ~~qt5-webengine~~ (need patch and version bump. ~~may work? if not gentoo has a patch? https://bugs.gentoo.org/831487~~)
- `vlc` (vlc4 will support ffmpeg5, there's a patch to build 3.x with ffmpeg5 but it will lack vaapi)
- `osg` (OpenSceneGraph plus `xine-lib`)
- `ytmdl` ? not sure but it uses `python3-ffmpeg-python` which being 6-8yr old I imagine is ffmpeg4
##### HAVE NOT BUILT YET (big-uns)
- omxplayer (rpi only?)
- kodi
- electron19
- ~~qt5-webengine~~ - some patches and version update
- ~~digikam~~ (qt5-webengine)
- ~~chromium~~ - ~~some patches but vaapi doesnt seem to be working~~ (use special flags)
##### UPDATED (for ffmpeg5)
- unpaper: update to 7.0.0.
- guvcview: update to 2.0.8.
- qt5: update to 5.15.8
- qt5-webengine: update to 5.18.13
- shiboken2: revbump for qt5.15.8 (patch)
- python3-pyside2: update to 5.15.8 (patch)
next prev parent reply other threads:[~2023-05-05 13:20 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 22:39 [PR PATCH] " zlice
2023-03-22 22:54 ` [PR PATCH] [Updated] " zlice
2023-03-22 22:59 ` zlice
2023-03-22 23:08 ` paper42
2023-03-22 23:09 ` [PR REVIEW] " paper42
2023-03-22 23:10 ` paper42
2023-03-22 23:10 ` paper42
2023-03-22 23:11 ` paper42
2023-03-22 23:19 ` paper42
2023-03-22 23:20 ` paper42
2023-03-22 23:25 ` zlice
2023-03-22 23:25 ` zlice
2023-03-22 23:28 ` paper42
2023-03-22 23:33 ` [PR PATCH] [Updated] " zlice
2023-03-22 23:36 ` [PR REVIEW] " zlice
2023-03-23 0:15 ` [PR PATCH] [Updated] " zlice
2023-03-23 2:05 ` sgn
2023-03-23 12:39 ` zlice
2023-03-23 12:50 ` [PR PATCH] [Updated] " zlice
2023-03-23 19:52 ` zlice
2023-03-23 20:01 ` zlice
2023-03-23 20:02 ` zlice
2023-03-31 13:03 ` zlice
2023-03-31 13:03 ` zlice
2023-04-04 13:18 ` zlice
2023-04-04 14:47 ` zlice
2023-04-23 15:23 ` zlice
2023-04-23 15:24 ` zlice
2023-05-05 13:20 ` zlice [this message]
2023-05-05 13:20 ` zlice
2023-05-05 13:20 ` zlice
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230505132044.uqJPGaQyv4jMvM1pxqdMt8d3rBOolRQYP5rjSrXCbVM@z \
--to=zlice@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).