Package Details: opera-developer-ffmpeg-codecs-bin 1:140.0.7339.81-1

Git Clone URL: https://aur.archlinux.org/opera-developer-ffmpeg-codecs-bin.git (read-only, click to copy)
Package Base: opera-developer-ffmpeg-codecs-bin
Description: Additional support for proprietary codecs for opera-developer using prebuilt FFmpeg binaries made for NW.js.
Upstream URL: https://github.com/nwjs-ffmpeg-prebuilt/nwjs-ffmpeg-prebuilt/
Licenses: LGPL2.1
Conflicts: opera-developer-ffmpeg-codecs
Provides: opera-developer-ffmpeg-codecs
Submitter: queenbiscuit311
Maintainer: queenbiscuit311
Last Packager: queenbiscuit311
Votes: 0
Popularity: 0.000000
First Submitted: 2024-04-30 06:44 (UTC)
Last Updated: 2025-09-12 03:35 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 Next › Last »

oech3 commented on 2025-07-31 09:19 (UTC) (edited on 2025-07-31 09:20 (UTC) by oech3)

I'm trying at nw-ffmpeg prebuilt to include compability info to release note. But PR will take many time to review.

oech3 commented on 2025-07-31 09:18 (UTC)

How about adding chromium-ffmpeg{,-legacy}-bin with pkgver=avcodec61.$_something without eopch and merging? Chromium based update cycle is very fast.

queenbiscuit311 commented on 2025-07-31 07:29 (UTC)

I'll try to find a way to get what commit ffmpeg prebuilt is using and if i can i'll decide whether its worth it to increase the epoch again

queenbiscuit311 commented on 2025-07-31 07:29 (UTC)

I'll try to find a way to get what commit ffmpeg prebuilt is using and if i can i'll decide whether its worth it to increase the epoch again

oech3 commented on 2025-07-31 02:36 (UTC)

by https://aur.archlinux.org/cgit/aur.git/tree/fetch-soname-by-chromium.sh?h=chromium-ffmpeg-codecs

queenbiscuit311 commented on 2025-07-30 21:05 (UTC)

How exactly do I get libavcodec version?

oech3 commented on 2025-07-30 06:50 (UTC)

I noticed that change of minor Chromium ver "could change" somane of libavcodec (between 137~138). So we should rely on version of libavcodec instead of Chromium version.

queenbiscuit311 commented on 2025-07-09 10:06 (UTC)

As far as I can tell, minor chromium version differences shouldn't matter. Not even all major chromium version changes break libffmpeg compatibility. Shouldn't be an issue to just set it to latest.

oech3 commented on 2025-07-09 10:00 (UTC)

I owned opera-developer-ffmpeg-codecs. Should source based package also sync minor version of Chromium? Or is bumping minor ver to latest OK to avoid updates?

« First ‹ Previous 1 2 3 Next › Last »