Mailinglist Archive: opensuse-factory (507 mails)

[Wolfgang Rosenauer <wolfgang@xxxxxxxxxxxxx>]

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@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx