Wow - what a bunch of clueless posters. Everyone read this:
http://www.fsf.org/news/blogs/licensing/more-about-the-app-store-gpl-enforcement
It explains exactly why the GPL license is incompatible with the App store. The general idea is that Apple puts further restrictions on your use of a binary... which is disallowed by the GPL.
That's all this is... it's just a license incompatibility.
It's not Apple being evil or Nokia.. or VLC or the FSF or Richard Stallman... it's just an incompatibility of licenses. Apple dictates certain terms... and those terms aren't compatible... therefore it's a no go.
Apple can either change it's terms to allow for something different (selectable by the apps author I would suppose) or VLC must change their license (or create a version of the code licensed under different terms). Note that VLC doing this is EXTREMELY unlikely... for one, because there are thousands of contributors that would each have to sign off on the relicense and two because they actually _like_ having the restrictions of the GPL in place so that VLC can't get used in ways they don't like.
It's also hard to see Apple giving alternative terms options to authors.... so the only logical conclusion is that it will get pulled.
It's not Apple's "fault" any more than it's "VLC's fault"... it's just a consequence of the two group's licenses...
http://www.fsf.org/news/blogs/licensing/more-about-the-app-store-gpl-enforcement
It explains exactly why the GPL license is incompatible with the App store. The general idea is that Apple puts further restrictions on your use of a binary... which is disallowed by the GPL.
That's all this is... it's just a license incompatibility.
It's not Apple being evil or Nokia.. or VLC or the FSF or Richard Stallman... it's just an incompatibility of licenses. Apple dictates certain terms... and those terms aren't compatible... therefore it's a no go.
Apple can either change it's terms to allow for something different (selectable by the apps author I would suppose) or VLC must change their license (or create a version of the code licensed under different terms). Note that VLC doing this is EXTREMELY unlikely... for one, because there are thousands of contributors that would each have to sign off on the relicense and two because they actually _like_ having the restrictions of the GPL in place so that VLC can't get used in ways they don't like.
It's also hard to see Apple giving alternative terms options to authors.... so the only logical conclusion is that it will get pulled.
It's not Apple's "fault" any more than it's "VLC's fault"... it's just a consequence of the two group's licenses...