| |||||||||||||
Tasting the Ice Cream SandwichTasting the Ice Cream SandwichPosted May 18, 2012 14:28 UTC (Fri) by xav (guest, #18536)Parent article: Tasting the Ice Cream Sandwich
I stopped reading the crypto implementation notes after this sentence: "The Android system tries to avoid incorporating GPL components, so using the cryptsetup command or libdevmapper were not available options.".
I find their anti-GPL bias to be bordering on religious stance.
(Log in to post comments)
Tasting the Ice Cream Sandwich Posted May 18, 2012 17:57 UTC (Fri) by dlang (✭ supporter ✭, #313) [Link]
while there's room to quibble over terminology (religious vs business stance), there's no secret that Android is avoiding using GPL in userspace.
At this point it doesn't really matter if the reasons for this position are valid or not, it's the position they are taking, and so GPL software is not an option for the programmers building Android core components.
Tasting the Ice Cream Sandwich Posted May 21, 2012 16:09 UTC (Mon) by paulj (subscriber, #341) [Link]
And yet Android's Bluetooth support depends on Bluez, which is GPL. Google seem to believe that wedging in some IPC is enough to "wash" away the GPL...
Tasting the Ice Cream Sandwich Posted May 22, 2012 19:56 UTC (Tue) by mirabilos (subscriber, #84359) [Link]
It actually is.
But trying to avoid the GPL isn’t so bad. Most BSDs do so, too. Less restrictions, less worries, you know, free spirits. (At least on the BSD side. On the other hand, Android/Google do give back to the OSS projects they add, even if the latter are BSD licenced, and even if Google is slightly evil.)
|
|||||||||||||