3 ms·
> I've never understood the problem with (L)GPL code on iOS devices. Sure, users don't have the possibility to replace the code on that platform. But the restri
by kelnos 3y ago
> I've never understood the problem with (L)GPL code on iOS devices. Sure, users don't have the possibility to replace the code on that platform. But the restriction is not imposed by the people distributing the code, but by external circumstances (Apple).
In the case of the App Store, Apple is the one doing distribution, so Apple must also comply with the terms of the license (in addition to the app developer). Apple has decided they will not do that (that is, people they distribute to will not have the ability to modify the LGPL code, relink the final executable, and run it on their devices), so Apple cannot legally distribute binaries that contain LGPL code.
It only makes sense, then, that Apple should preemptively reject apps that link in LGPL code, as they know that they will not abide by the licensing terms.
> If I have the OK from Tim Cook and all the secret signing keys, I can compile and run anything I want on my iOS device. And even without that, if somebody provides all the object files of non-LGPL code and build instructions, I can replace the LGPL code and run my own version outside of the app store.
That's not permitted by the license. The (L)GPL prohibits a third party from adding extra conditions to exercising the rights granted in the license. "Pay Apple for a developer account and get their permission" is an extra condition. Even if there is a jailbreak-y method of getting around the extra conditions, I don't think that would fly.
> Often when people ban (L)GPL code, its just a pretext, because they don't want to deal with the complexities or for other reasons.
Agreed, but I'm not convinced this is one of those cases.
- foota 3y agoDoes LGPL require that you be able to do so on the same platform it's being distributed on? There's nothing stopping someone from downloading an LGPL binary from the app store and running it in an emulator or something, right?
- cyphar 3y agoIn short, yes. See 4(e): > Provide Installation Information, but only if you would otherwise be required to provide such information under section 6 of the GNU GPL, and only to the extent that such information is necessary to install and execute a modified version of the Combined Work produced by recombining or relinking the Application with a modified version of the Linked Version. And from GPLv2: > For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable.
- foota 3y agoPerhaps this is splitting hairs (although that's necessary for licenses), but would it not be sufficient to be able to install the binary somewhere, but not on every machine? E.g., if I tell a customer the modified binary can be installed on some emulator, but not their phone, why is that prohibited? In this case, I guess the installation information would have to be "use an emulator and do XYZ".
- yreg 3y ago> It only makes sense, then, that Apple should preemptively reject apps that link in LGPL code, as they know that they will not abide by the licensing terms. But that's not the case at all. Apple is accepting apps that include LGPL code.