[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#199917 - A consensus on handling Mozilla plugins?

On Fri, Jul 11, 2003 at 03:36:55AM +1000, Andrew Lau wrote:
> On Thu, Jul 03, 2003 at 10:15:58PM +0200, Jerome Warnier wrote:
> There are currently 5 packages in unstable that dump plugins under
> /usr/lib/mozilla/plugins, not to mention several more contrib/non-free
> installers that do the same thing.
> http://packages.debian.org/cgi-bin/search_contents.pl?word=%2Fusr%2Flib%2Fmozilla%2Fplugins&version=unstable
> Does anyone have any suggestions as to how to handle plugins for
> mozilla, mozilla-snapshot and now mozilla-firebird in such a way that
> plugins are automatically symlinked/delinked whenever a new mozilla-like
> browser is installed? Where should they go?

IMO, plugins that use the Netscape 4 Plugin API (i.e., all plugins
that I know about) should install into /usr/lib/npapi/plugins/, and
browsers should add this to their plugin path.

The directory doesn't matter.  It could be /usr/lib/mozilla/plugins/
or /usr/lib/netscape/plugins.  "npapi" is more descriptive of the
interface that the plugins actually use, though.

> If I were to start writing an update-mozilla-plugins script for use in
> mozilla packages, what pitfalls might I encounter?

There's really no need.  Browsers just need to add a common directory
to their plugin path.

See also: #179175, #169404.


Reply to: