I will say, having spent (wasted) a few minutes parsing some of those issue threads, the attitude of the comments basically trying to strong-arm the author into using GPL kind of sucks, it's approaching a realization of all those delusional blogposts I read in the mid 00's about how the "viral nature" of GPL code is a threat to muh precious code I've written myself. At the very least, tell CE to not use the GPL'ed portions (I mean, from what I found, the actual violations are simple things, one is a script to convert text formats, another is literally a list of op-codes) and have them use something else or roll their own, those pieces shouldn't be hard to self-write.
I'm team free software and GPL code makes it more likely that people will GPL their code, but this sort of mobbing/bullying shouldn't be the way to do it. Let people make the decision because it is technically superior to do so, and sure ask people but bullying like this seems counter-productive.
As an aside for the tcc bits, they're right, tcc is lgpl, but it is odd that parts of it are stamped GPL proper, so I'm not sure what the protocol is there...is that an improper inclusion of GPL'ed code into a LGPL project? That would be tcc's fault then...
I'm team free software and GPL code makes it more likely that people will GPL their code, but this sort of mobbing/bullying shouldn't be the way to do it. Let people make the decision because it is technically superior to do so, and sure ask people but bullying like this seems counter-productive.
As an aside for the tcc bits, they're right, tcc is lgpl, but it is odd that parts of it are stamped GPL proper, so I'm not sure what the protocol is there...is that an improper inclusion of GPL'ed code into a LGPL project? That would be tcc's fault then...