Am 29.09.2016 um 21:30 schrieb Bill Allombert: > I would pick 2 in general because some users do not install Recommends > by defaut and I do not know how well gnome-twitch react when there is no > plugin,
When the user first tries to watch a stream, he will be prompted to choose one of the installed player backends. If there is none installed, he will just see an empty plugin list. If the user does not install recommended packages on purpose, he will hopefully know that he needs to install an additional package in such a case. But it would probably be nice to have a message telling him that he needs to install at least one backend instead of just an empty list, I will suggest that to upstream. and "apt-get autoremove" will take care of removing the > backends. Only the automatically installed one. If the user installs gnome-twitch, then gnome-twitch-player-backend-gstreamer-cairo will be automatically installed. If the user then decides he wants to use the mpv backend, he will install gnome-twitch-player-backend-mpv. If he later decides to uninstall gnome-twitch, "apt-get autoremove" will only remove the automatically installed gnome-twitch-player-backend-gstreamer-cairo, but not the manually installed gnome-twitch-player-backend-mpv. > What you can also do is to use a metapackage gnome-twitch-backend that > all backend provides. This does not solve the circular dependency but > this way you do not need to hard-code a list of backends. I thought about using a virtual package, but decided against it, because as far as I know, I can not declare a dependency on a specific version of a virtual package, and the Plugin-API of gnome-twitch is not guaranteed to be stable (yet?). So I would still want to go for option 3, once the empty plugin list contains a message telling the user to install a backend. Sincerely, Tim Dengel
