4 ms·
It doesn't appear they're objecting to the source-code distribution (which is allowed to be separate from the binary), but to the app store's license terms for
by _delirium 16y ago
It doesn't appear they're objecting to the source-code distribution (which is allowed to be separate from the binary), but to the app store's license terms for apps: http://www.apple.com/legal/itunes/appstore/dev/stdeula/ http://www.apple.com/legal/itunes/appstore/dev/stdeula/
Since GNU Go is under the GPL, they're saying: you can't distribute it under Apple's "Licensed Application End User License Agreement", because that isn't a license the original author applied to the software, and the GPL prohibits you from piling on a new license.
This no-new-license-terms section of the GPL is to keep people from subverting the GPL by tacking on new terms to GPL'd software, which I believe includes EULAs. So, unless you're the original author and copyright holder (in which case you can always add whatever terms you want), you can't tell end users something like: "it's GPL, but here are more rules you have to follow if you want a copy [click yes to agree to these terms]". Since the App Store basically does that---it has an EULA that you have to agree to before you can get a copy of GNU Go---it falls afoul of that provision.
In practice it's more making a point, because Apple probably cannot really enforce any of the additional terms against users of a copy of GNU Go, and it's not clear they'd care about doing so. But it violates the FSF's principle that end-users should be able to modify the very copy of the software they receive, because it tacks on terms that amount to, "you cannot reverse-engineer or decompile this copy of GNU Go", which clearly isn't a condition the FSF itself, as the GNU Go copyright holder, would've added.
A workaround, if Apple cared enough, would be to exempt open-source apps from the EULA terms, because the terms are really mainly aimed at stopping reverse engineering, and there's no point in stopping reverse-engineering of apps which are already open source. (Android's app store avoids this problem entirely by not applying any default EULA, and leaving it entirely up to the app author which EULA, if any, they want to ship.)
- mtigas 16y agoI’ve wondered about these license conflicts for a while now, as I’d been tinkering away on a couple of apps I’m planning to open source. This is, hands-down, the clearest plain English explanation I’ve heard regarding the combination of GPL and App Store EULA.
- greendestiny 16y agoThe App Store allows custom EULAs though they have to meet some minimum terms. I have no idea if the minimum terms are GPL compatible (probably not you'd imagine).
- tghw 16y agoDon't those custom EULAs just supplement the Apple EULA? If so, that doesn't solve the problem.