|
|
|
|
|
by initplus
1504 days ago
|
|
There are more requirements than just making the source available. GPLv3 has an anti-Tivoization clause that forbids using GPLv3 code in a product in a way that the GPLv3 code is not able to be replaced by the end user. And there are also requirements that you distribute additionaal "Installation Information" alongside the code itself. If you have to release your code under GPL, you must make it possible for end users to build & run your code. Can't hide behind proprietary in-house compilers, build systems, or build time dependencies on proprietary data to prevent end users making use of the GPL'd source. https://www.gnu.org/licenses/gpl-faq.en.html#InstInfo "GPLv3 explicitly requires redistribution to include the full necessary “Installation Information.” GPLv2 doesn't use that term, but it does require redistribution to include scripts used to control compilation and installation of the executable with the complete and corresponding source code. This covers part, but not all, of what GPLv3 calls “Installation Information.” Thus, GPLv3's requirement about installation information is stronger." |
|