Android now forces apps to include proprietary code for push notifications

Re:Android now forces apps to include proprietary code for p... by striking on Monday June 10, 2019 @10:12AM (#20146861)

Your code is no longer completely FOSS when you do that. It depends on a binary blob that you can't see into.

[ Parent | on HN ]

Re:Android now forces apps to include proprietary code for p... by pfortuny on Monday June 10, 2019 @10:17AM (#20146909)

Yes, yes, but I guess BSD-licence-using developers do not care too much about it.

[ Parent | on HN ]

Re:Android now forces apps to include proprietary code for p... by dwaite on Monday June 10, 2019 @12:08PM (#20148035)

You absolutely can do this - this is how the Nvidia shim driver works after all.

What you can't do is write code which depends on GPL, then distribute it with those GPL components and insist the resulting package is not GPL.

In fact, it's not so much 'dependent than derivative. GPL is a copyright license, and copyright restrictions can only only flow to derivative works.

[ Parent | on HN ]

Re:Android now forces apps to include proprietary code for p... by astazangasta on Monday June 10, 2019 @10:57AM (#20147310)

Dependencies are different than source code. You can write FOSS that runs on Windows, which is a dependency and not FOSS.

[ Parent | on HN ]

Re:Android now forces apps to include proprietary code for p... by bscphil on Monday June 10, 2019 @12:13PM (#20148076)

As long as it doesn't require linking to a proprietary Windows library to interface with the NT api. That would violate at least the GPL 2. Though you could do it yourself, and release your own code as GPL (and the combined work as proprietary), no one else could distribute the full work under the GPL because of the incompatibility.

[ Parent | on HN ]

Re:Android now forces apps to include proprietary code for p... by richardwhiuk on Monday June 10, 2019 @03:38PM (#20150020)

You can ship so long as it's not statically linked.

[ Parent | on HN ]