[Bug 1806] Review request: Opera 11.50 beta

[RPM Fusion Bugzilla]

http://bugzilla.rpmfusion.org/show_bug.cgi?id=1806





--- Comment #3 from Patryk Obara <patryk.obara at gmail.com>  2011-06-18 00:41:09 ---
> Uh, normally, if the dependency generator detects a dependency, the stuff
> is really required, filtering out the dependencies is a very bad idea! (...)

I understand and totally agree. Opera is designed to look native in KDE4 and
Gtk based desktop environments (if neither is present during runtime, then
opera falls back to using it's own internal toolkit). To achieve this, browser
comes with two small libraries (liboperagtk.so and liboperakde4.so) - we filter
out are dependencies generated from these two files. They are NOT required -
e.g. if Gnome user installs Opera we don't want to force him into installing Qt
libraries only because Opera is capable of using them. Same goes for KDE user,
who does not have gtk libraries installed. And e.g. users of xmonad can still
use Opera and not install gtk neither Qt dependencies.

Now, why those dependencies are (properly) not picked up by internal generator
when packaging opera for 32bit arch? I don't know. But they are there on x86_64
and they are completely unnecessary.

Other filtered-out dependencies are 32bit libraries for
operapluginwrapper-ia32-linux. Similar story: if user installs 64bit browser
and have 64bit plugins installed, then there's no need for 32bit dependencies.
And if he wants to use 32bit plugin, then dependencies should be provided
either by this plugin or nspluginwrapper.

> What's wrong with nspluginwrapper? Why does Opera need its own?

operapluginwrapper is dummy application, that Opera uses to detach plugin into
completely separate process. We were first *nix browser to implement this (in
2007) and it works pretty well :) It purpose is similar to firefox'
plugin-container process (introduced in 2010).


-- 
Configure bugmail: http://bugzilla.rpmfusion.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You are the assignee for the bug.