| ▲ | 15155 11 hours ago | ||||||||||||||||
GPLv3 doesn't entitle you to signing keys or the ability to remove them: you can release, compile, and inspect the source which will ostensibly still be provided - but not practically use it on the hardware you purchased. | |||||||||||||||||
| ▲ | mananaysiempre 11 hours ago | parent | next [-] | ||||||||||||||||
It very much does. > “Installation Information” for a User Product means any methods, procedures, authorization keys, or other information required to install and execute modified versions of a covered work in that User Product from a modified version of its Corresponding Source. The information must suffice to ensure that the continued functioning of the modified object code is in no case prevented or interfered with solely because modification has been made. > If you convey an object code work under this section in, or with, or specifically for use in, a User Product, and the conveying occurs as part of a transaction in which the right of possession and use of the User Product is transferred to the recipient in perpetuity or for a fixed term (regardless of how the transaction is characterized), the Corresponding Source conveyed under this section must be accompanied by the Installation Information. But this requirement does not apply if neither you nor any third party retains the ability to install modified object code on the User Product (for example, the work has been installed in ROM). | |||||||||||||||||
| ▲ | yjftsjthsd-h 11 hours ago | parent | prev [-] | ||||||||||||||||
Okay, I'll bite. What do you think is the difference between GPLv2 and 3? | |||||||||||||||||
| |||||||||||||||||