Is Apple Now Blocking Contributions To GCC?
|
|
|
Comments (2)
If GCC is licensed under the GPLv2/3, then two things are true:
1. Apple must supply whatever patches they have applied to the GCC source code base, as well as (a link to?) the source code base to which they apply those patches, for whatever Apple-published version a user may obtain, and Apple must supply these on demand of anyone to whom Apple has supplied the binaries built from these.
2. Once someone receives these (source code plus patches), Apple cannot restrict what the recipient does with them, as long as the recipient complies with the terms of the GPLv2/3. An NDA would violate both versions 2 and 3 of the GPL.
So what's to stop someone from demanding, and then publishing the patches where the GCC project can find them?
1. Apple must supply whatever patches they have applied to the GCC source code base, as well as (a link to?) the source code base to which they apply those patches, for whatever Apple-published version a user may obtain, and Apple must supply these on demand of anyone to whom Apple has supplied the binaries built from these.
2. Once someone receives these (source code plus patches), Apple cannot restrict what the recipient does with them, as long as the recipient complies with the terms of the GPLv2/3. An NDA would violate both versions 2 and 3 of the GPL.
So what's to stop someone from demanding, and then publishing the patches where the GCC project can find them?
Post a comment
A free account is needed to post. Write your comment here first: your text is kept in this browser while you sign up or log in, and is waiting for you when you come back.
Your message:Markdown: **bold**, *italic*, [text](https://link), - lists, > quotes, $x^2$ for math. Formatting help
Sign up and post (it is free) or Log in and post

I think that I am super happy I did not buy into the Apple product line. I have no commitment to developing for a me-only company.