On 22.04.2015 08:41 PM, Ryan Schmidt wrote: > > On Apr 22, 2015, at 1:23 PM, Mihai Moldovan wrote: >> >> You're right. The proper solution would be to add the old driver-driver back >> to FSF GCC and get it upstreamed, instead of relying even more on muniversal. >> >> Personally, I do not wish to do so, for multiple reasons. > > Too bad Apple didn't contribute the code back to FSF. Or maybe they did and > they didn't accept it for some reason? I don't know. But this is the kind of > thing I hate about forking projects.
FSF GCC is licensed as GPLv3. Apple does explicitly not allow usage of its code under GPLv3 for some reason I have forgotten, but only GPLv2. There might have been other (technical) reasons for rejecting the changes Apple did to GCC, but AFAIK that was the biggest disagreement. Mihai
signature.asc
Description: OpenPGP digital signature
_______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
