Re: [opensuse-factory] new Firefox feature (call for help)
Wolfgang Rosenauer wrote:
Currently that is not possible with our repos because there are two things I think: we would need to add the metadata (probably using defined Provides keywords would do) _and_ we would need a special repo parser which could read from defined repos but both could be solved at some point.
So to sum up again. I'm quite undecided what the right thing is.
Ah, I see. I didn't know about the ubuntu plugin. We should probably keep this plugins as similar as possible. Package flash-player already has Provides symbol for mimetype: $ rpm -q flash-player --provides netscape-plugins libflashplayer.so mimetype(application/x-shockwave-flash) flash-player = 10.0.22.87-0.1.1 But that's not true for java or moonlight packages. We can add also other Provide symbol, for example plugin({ec8030f7-c20a-464f-9b0e-13a3a9e97384},libflashplayer.so) If we go through the packages and and these two symbols to them, then we could build a database you need from the repository data. -- Best Regards / S pozdravom, Pavol RUSNAK SUSE LINUX, s.r.o Package Maintainer Lihovarska 1060/12 PGP 0xA6917144 19000 Praha 9, CR prusnak[at]suse.cz http://www.suse.cz -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Tuesday 30 of June 2009 01:28:55 Pavol Rusnak wrote:
Wolfgang Rosenauer wrote:
Currently that is not possible with our repos because there are two things I think: we would need to add the metadata (probably using defined Provides keywords would do) _and_ we would need a special repo parser which could read from defined repos but both could be solved at some point.
So to sum up again. I'm quite undecided what the right thing is.
Ah, I see. I didn't know about the ubuntu plugin. We should probably keep this plugins as similar as possible.
Package flash-player already has Provides symbol for mimetype:
$ rpm -q flash-player --provides netscape-plugins libflashplayer.so mimetype(application/x-shockwave-flash) flash-player = 10.0.22.87-0.1.1
But that's not true for java or moonlight packages. We can add also other Provide symbol, for example
As Wolfgang told me, the 'Provide: mimetype(foo/bar)' is generated from .desktop file. I'm going to add the plugin desktop file to java-1_6_0-{sun,openjdk}-plugin in Factory.
plugin({ec8030f7-c20a-464f-9b0e-13a3a9e97384},libflashplayer.so)
I have never understood what the Firefox strings '{ec8030f7- c20a-464f-9b0e-13a3a9e97384}' means and where they comes. Is this a global identifier of susefox plugin, or something else? I can add this to java packages too, if you'll need this. Wolfgang: the java plugin is specific, because we have two implementations of Java plugin: * openjdk - open source, but sometimes it might not work (even things goes better) * sun - non-free, but should works everywhere This situation will probably not solved, because even Sun claims that they will opensource it, no one believe it, so RedHat developers works on own implementation under the IcedTea project. Can your plugin work with it? Regards Michal Vyskocil -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Michal Vyskocil schrieb:
Package flash-player already has Provides symbol for mimetype:
$ rpm -q flash-player --provides netscape-plugins libflashplayer.so mimetype(application/x-shockwave-flash) flash-player = 10.0.22.87-0.1.1
But that's not true for java or moonlight packages. We can add also other Provide symbol, for example
As Wolfgang told me, the 'Provide: mimetype(foo/bar)' is generated from .desktop file. I'm going to add the plugin desktop file to java-1_6_0-{sun,openjdk}-plugin in Factory.
plugin({ec8030f7-c20a-464f-9b0e-13a3a9e97384},libflashplayer.so)
I have never understood what the Firefox strings '{ec8030f7- c20a-464f-9b0e-13a3a9e97384}' means and where they comes. Is this a global identifier of susefox plugin, or something else? I can add this to java packages too, if you'll need this.
The above mentioned string is a unique identifier for Firefox. I'd say that's not that important in the first step as plugins meant for Firefox are supposed to work in seamonkey as well (or any other browser which supports npapi). So the two (three) most important things we need to know from a plugin are - the mimetypes it supports (that could be done using the desktop file while I'm not sure if that should be reused for plugin stuff as I've thought it's meant for desktop apps). - the fact it is a npapi plugin "netscape-plugins" could be used actually (- the plugin filename to support the new selection feature in susefox)
Wolfgang: the java plugin is specific, because we have two implementations of Java plugin: * openjdk - open source, but sometimes it might not work (even things goes better) * sun - non-free, but should works everywhere
This situation will probably not solved, because even Sun claims that they will opensource it, no one believe it, so RedHat developers works on own implementation under the IcedTea project. Can your plugin work with it?
The addon can offer multiple plugins for a mimetype and it can be controlled to which product they apply (as seen above). Imagine the current Firefox <-> seamonkey issue in 11.1 where one isn't even supposed to work for the other. We can even control the order the plugins are displayed in the UI but the user would have the final choice which one to install. So now _if_ the java plugins would have different filenames I think we could even install more at the same time. That should work with a patch we have in Firefox 3.5 (would have to be ported to seamonkey and I'm not sure how other browsers would handle that). Actually we already have three Flash implementations and the addon can handle that already. You can choose which one to install and if you have all three installed, you can choose via the custom selector which one should be used. Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Hi, Pavol Rusnak schrieb:
Wolfgang Rosenauer wrote:
Currently that is not possible with our repos because there are two things I think: we would need to add the metadata (probably using defined Provides keywords would do) _and_ we would need a special repo parser which could read from defined repos but both could be solved at some point.
So to sum up again. I'm quite undecided what the right thing is.
Ah, I see. I didn't know about the ubuntu plugin. We should probably keep this plugins as similar as possible.
Package flash-player already has Provides symbol for mimetype:
$ rpm -q flash-player --provides netscape-plugins libflashplayer.so mimetype(application/x-shockwave-flash) flash-player = 10.0.22.87-0.1.1
But that's not true for java or moonlight packages. We can add also other Provide symbol, for example
plugin({ec8030f7-c20a-464f-9b0e-13a3a9e97384},libflashplayer.so)
If we go through the packages and and these two symbols to them, then we could build a database you need from the repository data.
How could we proceed here? So we can use "Provides", right? Almost all plugins are made for browsers so we can probably ignore the Firefox uuid of ec8.... and only provide the supported mimetypes and the plugin filename? The prefix should probably be npapi as it the the most exact phrase for that type of plugins. Using the mimetype as read from a desktop file is probably not the right thing. I'm not sure what format is allowed/possible in virtual provides but we have to plan for multiple mimetypes so what would be a possible format for multiple mimetypes and the filename? Who can decide if we do that for every plugin package and extend the package conventions with that information if we agreed on it? Thanks, Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (3)
-
Michal Vyskocil -
Pavol Rusnak -
Wolfgang Rosenauer