Hi all, wow, that was an interesting discussion today. Unfortunately I could not follow it directly since my real job currently takes most of my time.
After digging throw most of the thread I see following points that are relevant for my current problem: - Cdrdao cannot be GPLd as long as parts of it are not compatible with the GPL. It is very questionable if the "just linking to a library" argument would work here. - Modifying/restricting the GPL terms may be not allowed and would not make much sense anyway because it would be in fact a new license and not the GPL anymore. This would make the handling of cdrdao difficult for distributions and for other projects that want to base work on cdrdao. - Changing the license terms of cdrdao may be illegal because there were contributions to cdrdao which I would not call "minor". Even if it would be legal to do that in Germany I think it would be not nice and against the common sense. At the end, my conclusion is to not change the license of cdrdao which gives me following two options: 1. Freeze the project until the affected sources are replaced by a GPL compliant version. 2. Release a cdrdao version which temporarily omits the affected sources until a GPL compliant version is available. To save some work I'll go with the first option and start implementing the required Reed-Solomon coder. I've removed all releases from sf.net. Good night, Andreas -- Andreas Mueller Tel: +49 89 67808848 Ramsmeierstr. 1 Email: [EMAIL PROTECTED] 85579 Neubiberg, Germany -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
