- May 22, 2017
- 3,102
- 7,555
As Ren'Py team suggests:Well, thing is LGPL allows proprietary software to use libraries licensed under it, but proprietary software has to be separated. That's why most of such software actually uses system wide shared libraries. If they ship said libraries with software, then it qualifies as derivative work, and by letter of LGPL cant be copyrighted. If you take any RenPy game, it has said libraries shipped with it, under libs. It doesn't use system wide shared libraries.
RenPy is not LGPL licensed, it's licensed under MIT, yet for purpose of LGPL, it's derivative work of LGPL, and precisely because of it, all requirements of LGPL have to be met. Actually, RenPyYou must be registered to see the linksabout it.
RenPy games, are RenpPy, not product of it, but RenPy which runs series of pictures and text.
What they can copyright?
Characters? I am not sure they can.
Their code contributions? It's already open sourced. IE, it's enough to decompile rpc and rpa files, and you can see everything, reverse engineer and what's not. Not to mention it's shipped and cant work without LGPL libraries.
Story... well yes. But it has to be separated in order to
Well, yes, but if they extract their own work from , there is no the game. Why somebody of those actually making a lot of money, like Summertime Saga or ICSTOR never tried to claim copyright?
PS; for automatic part. I already wrote about it. Berne convention does not mention software, not surprisingly as it's legal document of XIX century. Some countries, like US or Germany, interpret software as literary works, but it's applicable only in those countries. That's actually how piracy works, as soon as software is not linked with US DMCA complaints are simply ignored, but I digress here.
This should be enough to achieve compliance with everything that Ren'Py includes to every game distribution package.Although we are unable to provide legal advice, we believe compliance can be achieved by including a copy of this license with every copy of Ren'Py you distribute, and linking to this license from your project's README file or App Store description. We suggest using the wording:
This program contains free software licensed under a number of licenses, including the GNU Lesser General Public License. A complete list of software is available atYou must be registered to see the links.
Many commercial software products are shipped with libraries protected by LGPL. They do mention those libraries in their licences and have added LGPL licence to their documentation. These libraries can easily be separated from the rest of the files, as they exist as separate files or folders.
In every Ren'Py game distribution package the libraries, Ren'Py code and game files are placed into clearly separate folders/directories, so that all binaries, including LGPL'd ones can easily be separated from the rest of the files. Although
You must be registered to see the links
that "For proprietary software, code under the LGPL is usually used in the form of a shared library" does not mean that this is always the case.I believe that image and script files distributed with Ren'Py by default in the "Standard version" inside the 'game' subfolder should be covered by the Artistic Licence included to other licences on the Ren'Py web page.
Everything that a game dev creates (scripts, images, animations, sounds) is protected by copyright from the moment of creation in the EU:
You must be registered to see the links
For example, DAZ model files belong to their creators, but an image file that uses these models belongs to the person who combined those files and positioned the models and rendered the image. In a Ren'Py game distribution package those files are placed into a separate folder or rpa archive file.
Those image files are copyrighted to their creator, as well as all the script files he created.