Index | index by Group | index by Distribution | index by Vendor | index by creation date | index by Name | Mirrors | Help | Search |
Name: freshplayerplugin | Distribution: RPM Fusion |
Version: 0.3.11 | Vendor: RPM Fusion |
Release: 7.fc34 | Build date: Wed Feb 3 10:47:19 2021 |
Group: Unspecified | Build host: arm-builder10.home.rpmfusion.net |
Size: 923081 | Source RPM: freshplayerplugin-0.3.11-7.fc34.src.rpm |
Packager: RPM Fusion | |
Url: https://github.com/i-rinat/freshplayerplugin | |
Summary: PPAPI-host NPAPI-plugin adapter |
As you know, Adobe have suspended further development of Flash player plugin for GNU/Linux. Latest available as an NPAPI plugin version 11.2 will get security updates for five years (since its release on May 4th, 2012), but further development have been ceased. Fortunately or not, newer versions are still available for Linux as a part of Chrome browser, where Flash comes bundled in a form of PPAPI plugin. PPAPI or Pepper Plugin API is an interface promoted by Chromium/Chrome team for browser plugins. It's NPAPI-inspired yet significantly different API which have every conceivable function plugin may want. Two-dimensional graphics, OpenGL ES, font rendering, network access, audio, and so on. It's huge, there are 107 groups of functions, called interfaces which today's Chromium browser offers to plugins. And specs are not final yet. Interfaces are changing, newer versions are arising, older ones are getting deleted. For various reasons Firefox developers are not interested now in implementing PPAPI in Firefox. However that does not mean it cannot be done. The main goal of this project is to get PPAPI (Pepper) Flash player working in Firefox. This can be done in two ways. First one is to implement full PPAPI interface in Firefox itself. Other one is to implement a wrapper, some kind of adapter which will look like browser to PPAPI plugin and look like NPAPI plugin for browser. First approach requires strong knowledge of Firefox internals,and moreover additional effort to get the code into mainstream. Maintaining a set of patches doesn't look like a good idea. Second approach allows to concentrate on two APIs only. Yes one of them is big, but still graspable. Second way will be used for the project. It will benefit other browsers too, not only Firefox.
MIT
* Wed Feb 03 2021 RPM Fusion Release Engineering <leigh123linux@gmail.com> - 0.3.11-7 - Rebuilt for https://fedoraproject.org/wiki/Fedora_34_Mass_Rebuild * Fri Jan 01 2021 Leigh Scott <leigh123linux@gmail.com> - 0.3.11-6 - Rebuilt for new ffmpeg snapshot * Mon Aug 17 2020 RPM Fusion Release Engineering <leigh123linux@gmail.com> - 0.3.11-5 - Rebuilt for https://fedoraproject.org/wiki/Fedora_33_Mass_Rebuild * Sat Feb 22 2020 RPM Fusion Release Engineering <leigh123linux@googlemail.com> - 0.3.11-4 - Rebuild for ffmpeg-4.3 git * Tue Feb 04 2020 RPM Fusion Release Engineering <leigh123linux@gmail.com> - 0.3.11-3 - Rebuilt for https://fedoraproject.org/wiki/Fedora_32_Mass_Rebuild * Wed Aug 07 2019 Leigh Scott <leigh123linux@gmail.com> - 0.3.11-2 - Rebuild for new ffmpeg version * Mon May 27 2019 Vasiliy N. Glazov <vascom2@gmail.com> - 0.3.11-1 - Update to 0.3.11 * Mon Mar 18 2019 Vasiliy N. Glazov <vascom2@gmail.com> - 0.3.10-1 - Update to 0.3.10 * Mon Mar 04 2019 RPM Fusion Release Engineering <leigh123linux@gmail.com> - 0.3.9-5 - Rebuilt for https://fedoraproject.org/wiki/Fedora_30_Mass_Rebuild
/etc/freshwrapper.conf /usr/lib/.build-id /usr/lib/.build-id/0a /usr/lib/.build-id/0a/8ae8e3717adc6eb1d8b0afaad996b94f4e24d3 /usr/lib/mozilla/plugins/libfreshwrapper-flashplayer.so /usr/share/doc/freshplayerplugin /usr/share/doc/freshplayerplugin/ChangeLog /usr/share/doc/freshplayerplugin/README.md /usr/share/doc/freshplayerplugin/debugging-guide.md /usr/share/doc/freshplayerplugin/img-missing-pepflash.png /usr/share/doc/freshplayerplugin/known-issues.md /usr/share/doc/freshplayerplugin/source-guide.md /usr/share/licenses/freshplayerplugin /usr/share/licenses/freshplayerplugin/LICENSE
Generated by rpm2html 1.8.1
Fabrice Bellet, Mon May 9 20:50:07 2022