Originally posted by Hibbelharry
View Post
Announcement
Collapse
No announcement yet.
Sailfish OS "Hossa" Upgrades From The Old eglibc 2.19, But Still Relying On GCC 4
Collapse
X
-
-
You cannot link one binary with code you licensed under GPLv2 and code you licensed under GPLv3 together and ship it to a customer. You simply can't.
This is probably the only major problem of GPLv3 from the standpoint of a free software advocate. But, in some scenarios, it is a dealbreaker.
Really don't understand why Hibbelharry is getting so much hate here for sharing his insights and experience.
- Likes 4
Comment
-
Originally posted by ypnos View PostReally don't understand why Hibbelharry is getting so much hate here for sharing his insights and experience.
I've had several arguments with these types over the fact that you do quite often have to work with externally developed code under a license that may not be GPL v2-compatible and particularly not v3 where you can't just re-license it, replace with something under a GPL-license it or re-write it in-house. Every time they're just as oblivious to these kind of realities that you're going to be facing out in the real world and start accusing you of actually just wanting to do something untoward. Don't get me started on how angry they get when you bring up lGPL, BSD or Apache as less cumbersome alternatives to more featured GPL licenses.
My suspicion is that most of these people have either never done software development or are still in school.Last edited by L_A_G; 08 May 2019, 08:27 AM."Why should I want to make anything up? Life's bad enough as it is without wanting to invent any more of it."
- Likes 1
Comment
Comment