3 ms·
The rational is that you should be able to just install any asset from the store in your game and be good to go. With an LGPL asset now you have to let customer
by charcircuit 3y ago
The rational is that you should be able to just install any asset from the store in your game and be good to go. With an LGPL asset now you have to let customers be able to edit that addon and rebuild your game with it which would be a pain, and most developers do not want to give out the unity project files.
Having a simple licensing story for assets on the store lets users have trust in whatever they see they can use in their game worry free.
Edit: Removed bit about LGPL applying to the original code because of static linkage because it was incorrect and distracting from my point
- deleted 3y ago[deleted]
- adrian_b 3y agoWhat you say is not correct. Only linking with a GPL library makes GPL applicable to the whole program. This is the difference between LGPL and GPL. LGPL is a normal license that applies only to the library. Since glibc uses LGPL, if your theory had been true than almost all programs run on a Linux system, regardless of their origin, would have been covered by LGPL.
- charcircuit 3y agoThe LGPL code gets statically linked with the rest of your code which means that you have to provide the project files in order to be able to change the LGPL code.
- adrian_b 3y agoNo, you do not have to provide any project files, even when everything is linked statically. Static linking can be split into two linking steps, first everything except the LGPL libraries can be linked into a big ELF object file, which no longer contains any information about the internal structure and the internal symbols, exactly like an executable file. The only difference between such an object file and an executable is that it contains unresolved external references, like a dynamically-linked executable. Then in the second and final linking step, the big binary object file is linked with the LGPL libraries. For compliance with LGPL it is enough to offer access to the big binary object file for the users who would want to replace the LGPL libraries.
- charcircuit 3y agoPlease do not forget that we are talking about Unity. Unity doesn't let you split up linking like that. All the game and asset codes gets mixed together in a single step. Needing to split out and rig together some hacky solution is the reason why they don't want it in the assert store. As I said in my original comment Unity wants assets to be low friction to add to your project.
- shakow 3y ago> With an LGPL asset now you have to let customers be able to edit that addon and rebuild your game > so now your game code is also under the LGPL and you have to publish your game code. AFAIK, that's only true of the GPL, not the LGPL.
- palata 3y agoAs a side note, I believe that LGLv3 says that you have to provide instructions about how to do it, but with LGPLv2 is just has to be technically possible if you have access to the binary.