Control: clone -1 -2 Control: retitle -2 clementine: Third-party plug-ins should be packaged for Debian Control: found -2 clementine/1.3.1+git276-g3485bbe43+dfsg-1 Control: severity -2 minor Control: tags -2 - upstream
On 04-Sep-2017, Jonas Smedegaard wrote: > One of several functions of Clementine is to stream audio from cloud > service Spotify. Initially selecting that function triggers a > routine where Clementine (asks for concent and then) downloads and > installs a non-free binary driver. As discussed in bug#874295, I think there is a separate bug to be resolved here: the program should not download code for execution from a third-party website, when that code can instead be packaged for Debian and installed using the OS package manager. On 30-Nov-2017, Ben Finney wrote: > Thomas Pierson <cont...@thomaspierson.fr> writes: > > It's only if a user want to connect to a particular external > > service that a plugin file is downloaded and used. > > That is still a problem, IMO. It would be best if the program did > not do that, and instead prompted the user to install the non-free > package providing that plug-in. This (new) bug report requests that the program in Debian should not have the behaviour Jonas describes above. Instead, if there are third-party plug-ins to enable Clementine features, those plug-ins should be packaged separately for Debian, and only enabled by installing the Debian package. The license conditions of those third-party packages will determine whether they are in Debian, or in some other archive area. This bug report does not relate to that issue. Instead, this bug report requests the download and execution of third-party code should not happen preferring to have the third-party code packaged and managed by the Debian package manager. -- \ “… a Microsoft Certified System Engineer is to information | `\ technology as a McDonalds Certified Food Specialist is to the | _o__) culinary arts.” —Michael Bacarella | Ben Finney <bign...@debian.org>
signature.asc
Description: PGP signature
