@lnxw37b2 @sjw @lanodan you cant re-license the code, so worst case scenario someone would have to fork it

@xue @sjw @lnxw37b2 You absolutely can relicense code, this has been done numerous times in the free software world.

In fact if you fork, you probably have even less of an opportunity to relicense since you're likely not one of the authors and probably will have way more issues contacting all the authors.

@lanodan @sjw @lnxw37b2 that was case with doom and has no power of law. once gpl stays gpl

@xue @sjw @lnxw37b2 You're probably thinking about something like license revocation which AFAIK is a totally different thing.
But things like MIT→Apache-2 or GPL2→GPL3 (which are incompatible without something like "or later") absolutely can happen.
(I'm not a lawyer)

@lanodan @sjw @lnxw37b2 those licenses are literally the same thing and changes being made only for lawyers to be happy, jesus

@xue @sjw @lnxw37b2 Apache grants a patent, MIT doesn't, did you not follow the topic?
GPL versions I'm too lazy for all that lawyer crap.

But yeah for my programmer ass, basically all that matter is it being a libre license.

@lanodan @sjw @lnxw37b2 but sqlite is like 200 years old, you cant hold patent that long

@xue @sjw @lnxw37b2 Media decoders and cryptographic libraries often have patents in them but the part being granted is only a very specific part that's implementation-independent like an algorithm.

And IIRC patents are 25 years, SQLite is 22 years old (2000-05-09).