Hacker Read top | best | new | newcomments | leaders | about | bookmarklet login

What's the problem with GPLv2 licensed app?


sort by: page size:

What is wrong with gpl v2?

Maybe because it's incompatible with the GPLv2.

I'm curious to know why GPLv2 makes it difficult for your use-case. Are you developing software that your clients install or host themselves?

What's the problem in GPLv2 for a code analysis tool?

What's wrong with GPL2 for adoption?

AFAIK there's an issue with GPLv3.

The License was changed recently to GPLv2.

GPLv3 is cool as open source goes, but is pretty restrictive. Basically you can't link to it and distribute your app without it being open source. A company like Google can probably not use it.

I don't see anything problematic in GPLv2 if the software is running on your own machines.

There are also a lot of desktop apps that are GPLv2 that don't have the "or a later version" phrase, which makes them incompatible with GPLv3.

GPLv2

That is an additional issue but only concerns GPLv3. GPLv2 is restricted for the reasons I mentioned above.

GPLv2 doesn't work for in-kernel code, or for code that could be used as a library.

That seems a bit drastic. If the GPLv2 doesn't do what you want it to do, perhaps another license will work better?

It's a problem with GPLv3, but for most other open-source licenses (e.g. BSD MIT) it isn't.

Assuming this is aiming to be a Linux replacement, GPLv3 certainly isn't the right choice for a license.

GPLv2 is probably ok, GPLv3 probably isn't.

For GPLv2

Why GPL v2?
next

Legal | privacy