Trac is being migrated to new services! Issues can be found in our new YouTrack instance and WIKI pages can be found on our website.

Changes between Version 5 and Version 6 of WhyNoiOSVersion


Ignore:
Timestamp:
Aug 18, 2012, 2:58:49 PM (11 years ago)
Author:
John Bailey
Comment:

Correctly mention Pidgin's "GPLv2 or later" licensing, as EionRobb? pointed out.

Legend:

Unmodified
Added
Removed
Modified
  • WhyNoiOSVersion

    v5 v6  
    77In a nutshell, the Apple Developer Agreement is the biggest "problem" preventing a Pidgin build for iOS devices.  We won't quote the exact text here, but the Agreement ''requires'' that developers allow Apple to impose additional restrictions on applications above and beyond the application's own license.  Among these additional restrictions are the well-known "5-device limit" and a prohibition on redistribution of the application.  It is also quite clear from the terms of the Agreement that the developer of an application is ''not'' the distributor of the application in the App Store--Apple is.
    88
    9 The additional restrictions required by Apple directly violate the GPL Pidgin is licensed under (Pidgin is licensed as GPLv2, and cannot transition to GPLv3 for a number of reasons not suited for this topic).  GPLv2 forbids adding restrictions above and beyond those included in the GPL's own text, thus any distribution via Apple's App Store is a direct violation of the GPL.  This is the root of the problem.
     9The additional restrictions required by Apple directly violate the GPL Pidgin is licensed under (Pidgin is licensed as "GPLv2 or later," and cannot transition to GPLv3 for a number of reasons not suited for this topic).  GPLv2 forbids adding restrictions above and beyond those included in the GPL's own text, thus any distribution via Apple's App Store is a direct violation of the GPL.  This is the root of the problem.
    1010
    1111== Aren't There Workarounds For This? ==
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!