On Friday, 25 March, 2011 10:27 AM, Nikki Erwin C. Ramirez wrote: > I remember reading somewhere that GPL doesn't force you to actually ship the > source code with the binaries. You can ship JUST binaries, but you MUST > give the source code to anyone who requests it, meaning the source code > doesn't really need to be publicly published. Is this correct?
Of course. Read what I said. I said "make the source available to whoever you ship the binaries to." But if you ship it to anyone, what's to stop them sending the same code to someone else, or to the rest of the world for that matter? You cannot make them sign an agreement to limit their right to do so, because the GPL forbids such things. If you're the exclusive copyright holder for the code, then you are free to add such a clause, but then you wouldn't be releasing your code under the GPL anymore. Apparently, however, Google has complied with the GPL at least as far as the kernel is concerned, and you can get the sources from here: http://android.git.kernel.org/?p=kernel/tegra.git;a=tree;h=refs/heads/android-tegra-2.6.36-honeycomb;hb=refs/heads/android-tegra-2.6.36-honeycomb There are only a few other GPLed components out there. The rest either isn't GPL or copyright by Google, so tough luck on getting those until they say they'll release them. We'll probably have to wait for ice-cream sandwich by the middle of the year. -- The purpose of computing is insight, not numbers.
signature.asc
Description: OpenPGP digital signature
_________________________________________________ Philippine Linux Users' Group (PLUG) Mailing List http://lists.linux.org.ph/mailman/listinfo/plug Searchable Archives: http://archives.free.net.ph
