On Fri, 2002-11-29 at 22:32, Neil R Porter wrote: > OK, so as I see it, I cannot revoke the license on previous releases > (seems sensible, and the opposite seems untenable), but surely I would > be breaking that very license on those previous releases if I > subsequently bring out closed source code on the back of previously open > source code? As the author, you're not bound by the licence in any effective manner. Think about it: you can only sue someone for licence infringement if you have been damaged (i.e., you're the copyright holder), any old Joe on the street cannot launch an action. Who could sue you for breaking the GPL? No-one. This isn't a feature of the GPL, it's just copyright law. > Perhaps I can do this if I > am the only one who has the copyright on it? I'd have to get > permissions from the others if not? Yes, sorry if I didn't make that clear. You need to be sole copyright owner, or have copyright of all the code, or permission from the other copyright holders. > Again, I'd like to point out that I don't intend to do this, but I just > want to know where I stand. Especially since I know I'm going to get > questioned about this from potential users of the code. There is a very good GPL FAQ on the GNU site: http://www.gnu.org/licenses/gpl-faq.html The GPL is subtle in a number of ways people often don't understand. Cheers, Alex.
Attachment:
signature.asc
Description: This is a digitally signed message part