[Top][All Lists]

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

Re: A New Plugin Wizard (Re: a bug in default .mozconfig)

From: Giuseppe Scrivano
Subject: Re: A New Plugin Wizard (Re: a bug in default .mozconfig)
Date: Sat, 18 Aug 2007 01:09:20 +0200
User-agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.90 (gnu/linux)


Alexander Sack <address@hidden> writes:

> The problem with "generic" is that if you don't get them from your
> distribution, they mostly don't exist in a universal binary form for
> linux ...
Yes, I know "generic" is vague word here, the same i386 binaries we
are providing for GNU/Linux are compiled under Debian, I doubt they
will work everywhere correctly.

> I am not sure I understand what you mean (I use both, XPILocation +
> manualInstallation URL atm). I assume you think about adding multiple
> sources for the same plugin to the same result entry?
Yes, unless you have a way to find which distribution is used by the
client, if you will continue to use XPILocation + manualInstallation
as mozilla firefox does, you will not break anything with it and offer
the possibility even to mozilla firefox users (not only to GNU
Iceweasel ones :) ) to use this plugin finder service.
The other information, like the .deb file position can be send in
another field, if the browser is able to handle this additional data
then it will use directly the .deb file without consider the original
XPILocation; probably it will be better to inform the server side
script about which formats are supported to avoid every time to send a
complete list.

> My current approach wouldn't do that, but would treat each install
> source as a separate entry in the plugin database and thus you would
> get multiple options in the plugin finder result list (e.g. gnash from
> apt + gnash from somewhere else). Otherwise, I don't understand what
> you mean ... maybe rephrase. ;).
The plugin finder service can show many alternatives but can the
browser really handle them?  Let's say you have two separate entries
for a gnash, a .rpm and a .deb and admit I will choose to install the
.rpm file.  How can you use the .rpm file under Debian?  In the same
way, is it useful for a RPM based distribution see that there is a
.deb package available for that plugin?  Is it the right behaviour of
your idea or I didn't understand correctly? :)


reply via email to

[Prev in Thread] Current Thread [Next in Thread]