Package: obs-studio Version: 25.0.3-0-g3c78a8aa-1 Severity: wishlist Dear Maintainer,
OBS 25 supports the obs-browser plugin. Sadly, this is not an independently buildable module, and needs to be built as part of building the rest of OBS. I have had some conversations with the developers on this on the OBS discord and they confirmed this is by design and won't change. It is designed to be linked into the source tree at OBS build time and built that way. It is separated for development reasons only. The legacy obs-linux-browser plugin has retired in favour of the official plugin. Therefore, at present, I have to build my own packages of OBS to use the browser plugin. Many new features of OBS are likely to be dependent on the OBS browser plugin in future (as is already seen in the Windows version). I realize this feature relies on the Chrome Embedded Framework to work, so it may be challenging? Is there debian policy on CEF? It seems many "browsery" features of other products use this strategy these days rather than deal with the hideous mess that is modern browser standards. I hope that the official debian can somehow figure out a way to fix this. Thanks, Christian -- System Information: Debian Release: bullseye/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-4-amd64 (SMP w/24 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- no debconf information
