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

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

Latest Comments

1 2 3 4 5 6 Next › Last »

oech3 commented on 2025-09-08 19:44 (UTC) (edited on 2025-09-08 19:50 (UTC) by oech3)

Sad to have many duplicated copies of library packages... Best situation is linking every apps with system's ffmpeg (blocked by another things) and 0 Chromium specific ffmpeg pkgs on AUR.

Fix at upstream of non-free app is mostly impossible.

queenbiscuit311 commented on 2025-09-08 18:40 (UTC)

To be completely honest, as long as the packages work and are intuitive for any users attempting to find them, i really don't see why it matters. The current setup functions and it is extremely easy for anyone using any version of opera to identify what package they need. Merging packages just to avoid duplicates in exchange for making it less clear seems pointless. Not to mention that an exact match to the exact minor version of chromium isn't really important, as long as the library works

oech3 commented on 2025-09-08 16:50 (UTC)

Other Chromium pkgs are missing -bin package with proper Chromium src and many pkgs for them is not useful. If size less than 10 MB is probrematic, pkgbase is usable.

I can fetch binary with latest compatible ABI for each Chromium instead of major ver.

queenbiscuit311 commented on 2025-09-08 16:26 (UTC)

Merging the two packages and including two bins would make it confusing for people using opera-beta and also put extra files on people's computers, i'm not really sure I see the benefit. Also what do you mean by checking libavcodec ABI?

oech3 commented on 2025-09-08 16:04 (UTC)

How about including 2 bins at one pkg? They are already small.

Would you add me to sub-maintainer since I can check libavcodec ABI.

queenbiscuit311 commented on 2025-09-08 15:42 (UTC)

They will be duplicate until opera-developer switches to chromium 139 or opera and any other browser have desynced chromium versions, both of which I have seen happen. opera and opera-beta seem to always use the same chromium version so i will likely put them both to be based off of the same package as you suggested to avoid complete duplicate packages, but opera-developer needs its own package that can be updated independently, and opera-beta needs its own package so that people using opera-beta know what package they are meant to install, even if it's building the same package as opera-ffmpeg-codecs with a different directory

oech3 commented on 2025-09-08 02:00 (UTC)

They will be completely duplicate after opera switched to Chromium M138+ and also duplicates with vivaldi,nwjs,etc.... Please remove duplications at least for opera*s or add me to co-maintainer only for this.

oech3 commented on 2025-09-07 06:13 (UTC)

If name is problem, pkgbase=(opera-* ...) with symlink is possible. But it fills web interfaces.

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

Main issue is that it would be confusing for anyone attempting to get ffmpeg compared to now where the package name makes it obvious

1 2 3 4 5 6 Next › Last »