http://bugzilla.novell.com/show_bug.cgi?id=500197
User wolfgang@rosenauer.org added comment
http://bugzilla.novell.com/show_bug.cgi?id=500197#c1
Wolfgang Rosenauer changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |wolfgang@rosenauer.org
Platform|x86-64 |All
--- Comment #1 from Wolfgang Rosenauer 2009-05-02 03:14:35 MDT ---
Thanks for the report. I basically was aware that plugins are not really
integrated for xulrunner and its embedding apps.
There were no known use cases (to me) though and so the priority to support
that wasn't too high in the past.
I'm not sure about the best solution though:
1. /usr/lib/browser-plugins: not every plugin what is good for browsers is good
for _any_ xulrunner/embedding application. Keep in mind that adding a plugin to
the global xulrunner space will result in that plugin being loaded for _every_
xul/embed application which could be problematic.
2. any other special directory: has basically the same issue as 1. but also
means that the plugin packages need to be changed to support the second
directory.
3. copy plugins with version upgrades: problematic as moving files beneath RPM
is a bad thing and I don't know of a good solution.
My idea in the past was that the xulrunner-using application has to define
which additional plugin directory to use (as it's done in openSUSE's Firefox)
since only the application knows if it wants for example the usual browser
plugins or not.
It's pretty easy to achieve that by exporting
MOZ_PLUGIN_PATH with the additional plugin directory. I know that this needs
awareness of that requirement in the applications but I still think that's how
it's supposed to be handled.
Honestly I'm not sure how other distributions handle that but all the other
ideas have quite some critical drawbacks.
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
