4 ms·

Are you sure about that? http://trac.webkit.org/browser/trunk/Source/WebCore http://trac.webkit.org/browser/trunk/Source/WebCore Edit: I would greatly appreci

by GHFigs 15y ago

Are you sure about that? http://trac.webkit.org/browser/trunk/Source/WebCore http://trac.webkit.org/browser/trunk/Source/WebCore Edit: I would greatly appreciate an explanation of what is inappropriate about the above link.

xentronium 15y ago
Could downvoters explain what's wrong with link to webcore trunk?
- angusgr 15y ago
  I didn't downvote, and IANAL, but I believe I know the difference. When releasing a product with GPL/LGPL source, the requirement is to provide either the source or an offer to provide the source which corresponds to the exact version of the source code used in that product "on a medium customarily used for software interchange". So, if there were tags in the webkit repository that said "iOS-4.3.2", "iOS-4.3.3", etc. then Apple could take a tarball of it and someone requesting source could be provided with the tarball and optionally a link to the correct tag in the repository. However, waving in the general direction of the source repository and saying "it's all in there somewhere" doesn't constitute compliance. Even if one of the Safari versions tagged in that repository happens to be the exact source that ships in some iOS 4.x, Apple has to make that relationship clear because (AFAIK) iOS is the "product" in this case, not Mobile Safari, given that the two are indivisible from the end user's perspective. (Again IANAL, so this is all mostly based on lurking the Gpl-Violations.org list, reading their Vendor FAQ, and dealing with some reluctanctly GPL compliant companies.)
  - trythis5 15y ago
    This is what I'm guessing as well, but unless Apple uses heavily customized versions of WebCore for their iOS releases, this seems like a decidedly trivial violation. Doesn't excuse Apple, but hardly worth all this fuss. Also, seriously, downvoting both GHFigs' and xentronium's comments is pretty lame, folks. (Feel free to downvote mine: I'll never see the score.)
    - eli 15y ago
      I was under the impression that they do use a heavily customized version of WebCore.
    - saurik 15y ago
      The LGPL requires that I am able to take Apple's provided source code, make my own modifications, and somehow compile/link the result into the program that is using the binary build. And, for the record: Apple's provided source code (which /is/ heavily modified for the iPhone), when they do provide it, isn't even complete enough to compile (it is missing a bunch of code for the WAK* classes), so Apple has simply never been in compliance with this license.
mbrubeck 15y ago
WebCore trunk is neither the complete code nor the exact version that Apple ships in iOS. For that, you have to go to their "release" pages like this: http://www.opensource.apple.com/release/ios-43/ http://www.opensource.apple.com/release/ios-43/

by GHFigs 15y ago

xentronium 15y ago

Could downvoters explain what's wrong with link to webcore trunk?

angusgr 15y ago
I didn't downvote, and IANAL, but I believe I know the difference. When releasing a product with GPL/LGPL source, the requirement is to provide either the source or an offer to provide the source which corresponds to the exact version of the source code used in that product "on a medium customarily used for software interchange". So, if there were tags in the webkit repository that said "iOS-4.3.2", "iOS-4.3.3", etc. then Apple could take a tarball of it and someone requesting source could be provided with the tarball and optionally a link to the correct tag in the repository. However, waving in the general direction of the source repository and saying "it's all in there somewhere" doesn't constitute compliance. Even if one of the Safari versions tagged in that repository happens to be the exact source that ships in some iOS 4.x, Apple has to make that relationship clear because (AFAIK) iOS is the "product" in this case, not Mobile Safari, given that the two are indivisible from the end user's perspective. (Again IANAL, so this is all mostly based on lurking the Gpl-Violations.org list, reading their Vendor FAQ, and dealing with some reluctanctly GPL compliant companies.)
- trythis5 15y ago
  This is what I'm guessing as well, but unless Apple uses heavily customized versions of WebCore for their iOS releases, this seems like a decidedly trivial violation. Doesn't excuse Apple, but hardly worth all this fuss. Also, seriously, downvoting both GHFigs' and xentronium's comments is pretty lame, folks. (Feel free to downvote mine: I'll never see the score.)
  - eli 15y ago
    I was under the impression that they do use a heavily customized version of WebCore.
  - saurik 15y ago
    The LGPL requires that I am able to take Apple's provided source code, make my own modifications, and somehow compile/link the result into the program that is using the binary build. And, for the record: Apple's provided source code (which /is/ heavily modified for the iPhone), when they do provide it, isn't even complete enough to compile (it is missing a bunch of code for the WAK* classes), so Apple has simply never been in compliance with this license.

mbrubeck 15y ago

WebCore trunk is neither the complete code nor the exact version that Apple ships in iOS. For that, you have to go to their "release" pages like this: http://www.opensource.apple.com/release/ios-43/ http://www.opensource.apple.com/release/ios-43/