3 ms·
> Also, "effectively free if you make no changes" doesn't make sense -- free software requires you to have the freedom to make changes to the software. The GPL
by duskwuff 10y ago
> Also, "effectively free if you make no changes" doesn't make sense -- free software requires you to have the freedom to make changes to the software.
The GPL places some conditions on distribution; most notably, anyone distributing binaries is required to also make the source available. In the "standard" GPL, this applies even if the distributed binaries are compiled directly from the upstream source -- this is sometimes used as a "gotcha" to harass companies that use GPLed code (e.g, in embedded devices), but which fail to make every single piece of source code available for download. The exception granted by FreeRTOS makes perfect sense in this light.
- cyphar 10y ago> In the "standard" GPL This is only true for GPLv2. GPLv3 fixed this problem, as well as many other real problems (though I don't agree that it is as big of a problem as you claim). > The exception granted by FreeRTOS makes perfect sense in this light. Which exception is that? I read it as "this is kinda like the LGPL, but you also can't be 'competitive'". Also, none of this has anything to do with the statement "effectively free if you make no changes". Requiring you to provide the source does not make the software non-free.