- \r\n
- GPlv3 comes out and is more restrictive than GPLv2. \r\n
- I receive a program licensed GPLv2 "or any later version", and decide to distribute copies of it. \r\n
- In order to distribute copies, I choose to accept and abide by the terms of GPLv2. \r\n
- I offer to license copies GPLv2 "or any later version", and someone gets a copy from me which they then do something with which requires them to accept the terms of an applicable version of the GPL, and they choose GPLv3. \r\n
In step 4 above I've licensed a GPL program to a third party with additional terms more restrictive than those of the version of the GPL I agreed to when I decided to distribute. I would like to know, clearly and succinctly, how that is anything other than a clear-cut violation of Section 6 of GPLv2. Because, you see, I've read the license, and I know for a fact that there's not a damn thing in there which lets me add restrictions to the license when I distribute the program.
\r\n\r\nI know you've spouted nonsense previously about how "impose" means I have to force the choice, and that as long as I offer the less-restrictive v2 you don't think there's a problem. I'm of the opinion, however, that the "I didn't force it on him, your Honor" defense wouldn't hold up in court. Perhaps you should speak to an attorney regarding that, Ben.
\r\n\r\nAlso, I'd like you to meditate on the phrase "these terms and conditions" in Section 6 of GPLv2, and let me know exactly which terms and conditions are being referred to there.
\r\n\r\nAnd yes, the reductio was deliberately absurd; that was sort of the point. I've tried to keep this discussion light-hearted with the Monty Python taunts and exaggerated reductio and such, but if you want to keep up the petty ad-hominem shit I'll be happy to have a serious dick-measuring contest for our respective knowledge of intellectual property law.