FS#56699 - [mpv] compile with libsmbclient support (changes license)

Attached to Project: Community Packages
Opened by M. Ham. (MHami) - Wednesday, 13 December 2017, 09:57 GMT
Last edited by Christian Hesse (eworm) - Friday, 15 December 2017, 17:35 GMT
Task Type Feature Request
Category Packages
Status Closed
Assigned To Christian Hesse (eworm)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

Due to the ongoing relicense effort of mpv the libsmbclient module was disabled by default since it would make mpv GPLv3 only. It can be enabled using "--enable-libsmbclient" during waf configure and it says "enable Samba support (makes mpv GPLv3) [disable]".

Would that be a problem for ArchLinux to deliver a GPLv3 mpv and enable support for this?

Additional info:
* package version(s)
mpv 1:0.27.0-4

Steps to reproduce:
mpv can't play files accessed via smb:// protocol.
This task depends upon

Closed by  Christian Hesse (eworm)
Friday, 15 December 2017, 17:35 GMT
Reason for closing:  Fixed
Additional comments about closing:  mpv 1:0.27.0-5
Comment by Christian Hesse (eworm) - Wednesday, 13 December 2017, 10:09 GMT Comment by M. Ham. (MHami) - Wednesday, 13 December 2017, 10:26 GMT
Thanks for the response. Yeah, I know. The reason behind this is like I said: It would make mpv GPLv3. The question here is if it would be a problem for ArchLinux to deliver a GPLv3 mpv? It's a license issue for mpv since they want to release mpv under the LGPL per default. It's GPLv2 currently.

If that is an issue for ArchLinux as well it's OK. I am asking since ffmpeg also get's delivered in GPLv3 mode via --enable-version3
Comment by Christian Hesse (eworm) - Wednesday, 13 December 2017, 10:33 GMT
The question is whether or not we link against a library that is incompatible with GPLv3.
I will have to take some deeper looks.

Loading...