Bugzilla – Bug 118172
add totem plugin to firefox/mozilla
Last modified: 2005-10-04 20:08:51 UTC
---------------------------------------------- I have created a new plugin package - totem plugin. Package is named totem-plugin and installs: /usr/%_lib/browser-plugins/libtotem_mozilla.so /usr/%_lib/browser-plugins/libtotem_mozilla.xpt Could you add support for this plugin (i. e. creating symlinks). Please note, that the plugin is 64 bit on 64 bit platforms. Package was submitted to PLUS, too. ----------------------------------------------
Some issues: The plugin won't work on x86-64 as long as we don't ship the 64bit version of Firefox. So we only can handle the 32bit case for now. I think about dropping the whole plugin integration stuff with next version. Stanislav, do you think that makes sense? We already make sure the architecture fits by using lib and lib64. Can we trust all plugins in %{_libdir}/browser-plugins? Some other plugins which are not in browser-plugins need special attention still (as JRE). So I can't drop it easily. Any more thoughts?
current list (10.0) of plugins in browser-plugins: djvulibre RealPlayer dragonegg tclplug acroread flash-player mozilla-bonobo If they are all OK, we could just add the directory to the plugin infrastructure of Firefox.
But we have 64-bit mozilla, epiphany, (and galeon in supplementary). They don't have any plugin (with exception of mozplugger), which is able to play these files. I don't know all these plugins, but maybe we can modify mozilla to look at browser-plugins directory or link all plugins in SuSEconfig (instead of trigers). If there will be some problems, blacklist could be better than current whitelist. djvulibre Don't know. In 9.3 default installation, clicking to djvu image crashed my galeon/x86_64 immediately. I 10.0 it does not. I can test the plugin. RealPlayer OK dragonegg tclplug I don't know these plugin. acroread OK flash-player extremely unstable in 9.3-x86_64 mozilla-bonobo OK There is a specific problem in integrator plugins, like mozilla-bonobo and totem-plugin. Its MIME type list depends on external plug-ins (bonobo for mozilla-bonobo and gstreamer for totem). If there is no way to force re-caching MIME list, I plan to create work-around - touch file whenever plugin list changes.
(In reply to comment #3) > I don't know all these plugins, but maybe we can modify mozilla to look at > browser-plugins directory or link all plugins in SuSEconfig (instead of trigers). SuSEconfig is bad(TM), obsolete and should be avoided. (as far as I have been told some years ago) The directory can easily be added (env MOZ_PLUGIN_PATH should do it). > flash-player > extremely unstable in 9.3-x86_64 don't you mean gplflash? flash-player works for me w/o problems on 9.3-x86_64 > There is a specific problem in integrator plugins, like mozilla-bonobo and > totem-plugin. Its MIME type list depends on external plug-ins (bonobo for > mozilla-bonobo and gstreamer for totem). If there is no way to force re-caching > MIME list, I plan to create work-around - touch file whenever plugin list changes. The same for dragonegg which is the kparts plugin. So it's similar to mozilla-bonobo.
> flash-player > extremely unstable in 9.3-x86_64 Sorry. I mean gplflash. SuSEconfig is a good work-around of missing features in RPM. There are things, which cannot be done in RPM or extremely ineffectively. Dropping of SuSEconfig was delayed to undefined future. See bug 116756 as an example. I can imagine, that SuSEconfig will disappear if RPM will support: 1. Post-transaction scripts Script of defined name will be started only once after complete installation batch. This should be an addition to new %posttrans scriptlet. Without this feature, many scripts need to be started many times during batch installation (up to two times per package). %pretransscript /sbin/conf.d/SuSEconfig.gtk2 %s %preuntransscript /sbin/conf.d/SuSEconfig.gtk2 %s %posttransscript /sbin/conf.d/SuSEconfig.gtk2 %s %postuntransscript /sbin/conf.d/SuSEconfig.gtk2 %s %s will be names of RPM, which trigger this call 2. Modifiable path triggers. When any package installs or removes file in defined directory (complete directory list is not surely known in time of package installation), selected action will be performed. Without this feature, package cannot create specific caches without adding triggers to many other unrelated packages. Without path collection feature, package cannot change configuration of listed paths in path trigger. echo "/usr/share/applications /opt/gnome/share/applications" >/etc/opt/gnome/gtk2_cache.lst %triggerglob /sbin/conf.d/SuSEconfig.gtk2 /opt/gnome/share/icons/* /usr/share/icons/* or even: %triggerpath /etc/opt/gnome/gtk2_paths.d/*.lst or %triggerpathscript /opt/gnome/bin/collect_icon_paths
Firefox in STABLE does use /usr/lib/browser-plugins/ directly now.