Aaron Rainbolt on Nostr: npub1uvj0h…zv5uj npub1qg48c…0augv npub1xthsn…pu6wq If a project is isolated, ...
npub1uvj0hp5y5t3f6je5zc6c9pxz48jqzqqsnpw9avgzzpqaktspl9cshzv5uj (npub1uvj…v5uj) npub1qg48cy9nkrm0pkeuz7e9zrzeq2n6lnlwyn30u9zd0xe07g9qvras00augv (npub1qg4…augv) npub1xthsnnghl883w5wsjpknjk0jlapvejyepaqx3248ajwg697lc9qq5pu6wq (npub1xth…u6wq) If a project is isolated, yes, but when you start sharing code between projects, things get sticky if you don't have the "or later" clause. For instance if appA is GPLv2-only and appB is GPLv3-only, neither one can integrate code from the other, despite them both being fully FOSS applications. If appA is GPLv2-or-later and appB is GPLv3-or-later, appB can integrate from appA freely, and appA can "upgrade" to GPLv3-or-later and then be able to integrate changes from appB.
I've been the dev stuck with figuring out which flavor of GPL I'll be using for my app so as to not run afoul of the licenses of either of the apps I'm taking code from. It wasn't fun.
I've been the dev stuck with figuring out which flavor of GPL I'll be using for my app so as to not run afoul of the licenses of either of the apps I'm taking code from. It wasn't fun.