4 ms·
There's nothing stopping the next release of an application that has historically been GPL 2 or later being released as GPL 3.1 only, however? They can't go bac
by Macha 5y ago
There's nothing stopping the next release of an application that has historically been GPL 2 or later being released as GPL 3.1 only, however? They can't go back and take back the existing licenses to existing versions (the whole non-revocable term of the license) so other users can still give you those versions under those licenses even if the FSF decided they didn't want to themselves.
- squiggleblaz 5y agoThe following is crafted deliberately as something of a worst case scenario; I don't think it is even remotely likely. So GCC is 3.1 or later. RMS dies and Google, Facebook etc get in control of the FSF: after all, they are major contributors and beneficiaries. While this is going down, fearing the badness around the corner, the GCC project continues work on GCC under 3.1 only (and attempts to stop it, unsuccessfully). The FSF releases 4.0 which is a long and wordy version of 3 clause BSD. Google now forks the latest version of GCC before the project relicensed it. There are two versions continuing: Google GCC under GPL4+ and GCC GCC under GPL3.1. The community doesn't entirely know which branch to contribute to and amidst the mire all the new features of C++30 get added to a proprietary fork of Clang. In general, free software gets regarded as dusty and old and most development happens on compilers people bought.
- pjmlp 5y agoNo need for that. https://github.com/android/ndk/wiki/Changelog-r18 https://github.com/android/ndk/wiki/Changelog-r18 https://fuchsia.dev/ https://fuchsia.dev/