Winamp deletes entire GitHub source code repo after a rocky few weeks

Related: https://news.ycombinator.com/item?id=41662105

Winamp contained modified GPL code, violating the GPL (github.com/winampdesktop)

18 points by mepian 19 days ago | 6 comments

I can't see the original issue, but it's interesting that the title chooses to highlight the fact that the GPL code was modified. Actually, under the GPL, this fact is immaterial. If the Winamp player contained any GPL code at all, modified or not, then it is a derivative work of that GPL code and anyone receiving a copy of Winamp is entitled to demand the full corresponding source be provided under a GPL license.

> Actually, under the GPL, this fact is immaterial. If the Winamp player contained any GPL code at all, modified or not, then it is a derivative work of that GPL code and anyone receiving a copy of Winamp is entitled to demand the full corresponding source be provided under a GPL license.

That's just not true, surely? Lest everyone using any flavour of Linux is liable to the same problem?

How many apps out there are using GPL code? Android, for example.

Making a derivative in the sense of adding functionality to it, I get, but using it as-is as a component or library surely doesn't - and cannot - fall foul of the license else the entire technosphere is liable.

If you are linking against GPL code then yes it's true. If you are linking against LGPL code then it's fine. Note that running software on Linux doesn't mean you are linking to Linux. However, if you distribute Linux, then yes, you must supply the Linux source code on request.

The "technosphere" is generally fairly compliant on these things. There is no disaster. But this is also why most commercial companies avoid GPL libraries.