iceweasel/iceape plugin directory?
mh at glandium.org
Sat Dec 9 15:27:26 CET 2006
On Sat, Dec 09, 2006 at 02:50:45PM +0100, Matthias Klose <doko at cs.tu-berlin.de> wrote:
> Do these browsers use a common plugin directory, and/or can I use the
> firefox/seamonkey plugin directories?
Yes, for the moment, you'd have to use a local plugin directory for each
of the packages. And I don't think it would be wise to change that
before etch, but still, let's open discussion for after...
Mozilla maintainers, Konqueror maintainers, what would you think if we'd
standardize on a directory for plugins packages ? Or maybe several,
since there are different APIs. IIRC, there are NPAPI, XPConnect and
NPruntime, the latter being supposed to be the only one used for new
plugins, but I think there are still XPConnect-based plugins out there.
Something like /usr/lib/npapi-plugins for old NPAPI and
/usr/lib/npruntime-plugins for newer NPruntime API, etc., maybe...
Then plugin maintainers would put plugins choosing the directory
depending on the API it implements.
At the other end, programs would look up plugins in directories for
which they support the API. I doubt konqueror implements XPConnect, for
On the other hand, if plugins using a non-supported API on a browser would
just fail to load, we could just use an unique directory...
What do you all think ?
More information about the pkg-mozilla-maintainers