python-mpv icon indicating copy to clipboard operation
python-mpv copied to clipboard

Contradictory license information

Open mgorny opened this issue 3 years ago • 4 comments
trafficstars

Right now the project has some contradictory information regarding its license:

  • the notices on top of Python files indicate that their content is covered by GPL-2+
  • license in setup.py says GPL-3+
  • trove classifiers say GPL-2+ and LGPL-2+

Could you please clarify which one is correct, and fix the remaining instances?

mgorny avatar Apr 24 '22 20:04 mgorny

True, I typo'ed the one in setup.py. Originally, python-mpv was licensed under AGPLv3+. I have since changed over the license to match mpv's license, which is your choice of GPLv2+ or LGPLv2+. I'll fix setup.py to say GPLv2+, since I don't know how to set multiple licenses there.

jaseg avatar Apr 27 '22 12:04 jaseg

Another question, why not referring the possibility of lgpl in the mpv.py File. As far as I understood the license text stated in GitHub it depends on the build process of mplayer?! In the end the question is, if I use a LGPL version of mPlayer, is the mpv.py also under LGPL available?

ChrisLambert1 avatar Jun 28 '22 19:06 ChrisLambert1

Yes, that is correct. When you use it along an LGPL libmpv, python-mpv is also LGPL.

jaseg avatar Jun 30 '22 11:06 jaseg

Thank you for that answer, but as an improval it would be great, if this would be stated in the header of the mpv.py file.

It will be appreciated, if there would be a reference that it is possible to use your module under LGPL, depending on the used license for mplayer. So why not just putting a brief intro in the header of mpv.py, as it's done in your GitHub repository -> License: " python-mpv inherits the underlying libmpv's license, which can be either GPLv2 or later (default) or LGPLv2.1 or later. For details, see the mpv copyright page. " and extend it by: "Depending on the license used in combination with mplayer, the same license is applicable for this piece of code." "Uses license agreements could be found in: License.GPL or License.LGPL "

Or make it easier:

Just extend / enter a header (s. epydoc definition) after the module description in the mpv.py file including possible licenses:

author = "You" copyright = "Copyright 2007, The Project" credits = ["to who is involved"] license = "GPLv2+", "LGPLv2+" version = "x.x.x" maintainer = "***" email = "myMail" status = "Release"

Regards, Chris

ChrisLambert1 avatar Jun 30 '22 12:06 ChrisLambert1