10 messages in com.googlegroups.android-internalsRe: Android's GPL violations| From | Sent On | Attachments |
|---|---|---|
| TomCooksey | 19 Nov 2007 14:44 | |
| dasGrunge | 19 Nov 2007 15:28 | |
| TomCooksey | 20 Nov 2007 00:23 | |
| gaz | 20 Nov 2007 08:38 | |
| omattos | 20 Nov 2007 09:23 | |
| Brian Swetland | 22 Nov 2007 02:33 | |
| Rod Whitby | 22 Nov 2007 02:38 | |
| Brian Swetland | 22 Nov 2007 02:47 | |
| Rod Whitby | 22 Nov 2007 02:53 | |
| Dan Morrill | 22 Nov 2007 10:42 |
| Subject: | Re: Android's GPL violations |
|---|---|
| From: | dasGrunge (gdsc...@gmail.com) |
| Date: | 11/19/2007 03:28:01 PM |
| List: | com.googlegroups.android-internals |
On Nov 19, 5:44 pm, TomCooksey <TomC...@googlemail.com> wrote:
Now we know a bit more, I'd like to start this thread to list possible/ probable GPL violations within Android.
1) The Linux kernel: There's no config for the qemu kernel, only the halibut dev kit kernel. I'm pretty sure the config is a requirement of the GPL.
2) OpenBinder, which seems to form the basis of Android is released under the Mozilla Public Licence. I think this means Google must provide access (or instructions to access) the original source and describe what modifications they have made to that source. Anything using that source needs to be released under the MPL.
I'm not too familiar with the MPL, but the .config bit I'm certain about. BT got into a bit of bother about not releasing the .config file for the HomeHub.
Standard IANAL applies.
The config I believe is available in the emulator in /proc/config.gz. You can get it from there.
Having said that, I'm sure there are other open source licensing infringements, e.g. whichever libc library they're using. The promise to release the source at a future date not too far away might suffice