On Fri, Nov 20, 2015 at 07:08:20PM +1100, Tim Lunn wrote: > I discussed this with Alberto earlier in the year, and we went ahead > and landed the split in Ubuntu last cycle, but seems I never got > around to forwarding on the changes. Patches to follow. > > https://bugs.launchpad.net/ubuntu/+source/grilo-plugins/+bug/1394731
Ok, so I could finally sit down a bit and take a look at the split that you propose. I have some doubts, however. As I see it, plugins should only go to the -extra package if they require additional dependencies and they are not useful for most users. Is this also your criteria, or do you have other concerns? However, I've seen that that almost all plugins have the same dependencies as libgrilo itself (glib, libxml, libsoup, libsqlite, ...), so I see no reason why they should go to -extra. However you're putting there some of them: - dLeyna - Magnatune - Podcasts Then there's the Lua Factory plugin, that enables 10 extra built-in plugins: - Apple trailers - Euronews - Metrolyrics - Musicbrainz cover art - Spotify - ... The Lua plugin only depends on liblua, itself a small C++ library with no special requirements. From the plugins that you would put in the -extra package only DAAP and Freebox seem to have additional dependencies, and even those are quite standard for a GNOME desktop. What are the ones that concern you the most to have in the main package, and why? Berto
