I'm looking at grilo, and it seems mostly fine (except a test suite that isn't being run; I'm looking at enabling that). However... grilo also pulls in grilo-plugins via a recommends (and needs it to actually be useful).
grilo-plugins looks to be more problematic. There are additional packages that would need to enter main (libgupnp-av-1.0-dev and libtracker-sparql-0.14-dev), and there would need to be a security review, which I'm guessing would turn up a couple things.
So... A few options:
* Move grilo-plugins from Recommends to Suggests for grilo. That allows us to build totem and rhythmbox with support for grilo, and drop that delta. Users and flavors could still install grilo-plugins if desired.
* Review the plugins and split grilo-plugins into main-acceptable ones and ones that should stay in universe.
* Review the plugins and disable the ones that aren't main-acceptable.
Timo, you asked for grilo. Do you have an opinion?
I'm looking at grilo, and it seems mostly fine (except a test suite that isn't being run; I'm looking at enabling that). However... grilo also pulls in grilo-plugins via a recommends (and needs it to actually be useful).
grilo-plugins looks to be more problematic. There are additional packages that would need to enter main (libgupnp- av-1.0- dev and libtracker- sparql- 0.14-dev) , and there would need to be a security review, which I'm guessing would turn up a couple things.
So... A few options:
* Move grilo-plugins from Recommends to Suggests for grilo. That allows us to build totem and rhythmbox with support for grilo, and drop that delta. Users and flavors could still install grilo-plugins if desired.
* Review the plugins and split grilo-plugins into main-acceptable ones and ones that should stay in universe.
* Review the plugins and disable the ones that aren't main-acceptable.
Timo, you asked for grilo. Do you have an opinion?