cdrtools - a tale of two licenses [LWN.net]

cdrtools - a tale of two licenses

Posted Aug 13, 2006 13:08 UTC (Sun) by k8to (subscriber, #15413)
In reply to: cdrtools - a tale of two licenses by dmantione
Parent article: cdrtools - a tale of two licenses

Is that you Jörg?

Again, it does not matter whether the GPL work "contains scripts". The GPL requires that the necessary scripts used to build the work be made available under the same terms as the source, that is under the GPL. It does not matter whether these scripts are "part of the work". If they are not available under the GPL, then the GPL license is not satisfied, and you are not granted permission to redistribute.

Now, in this case the scripts and program are authored by the same person. If he is the exclusive copyright holder, it is possible he could certainly modify the license under which the program is distributed to make it a GPL program with the added permission that the script system he authors under CDDL may be used as a substitute. (It is possible I misunderstand what kinds of special exceptions may be provided.) However, even if this is possible, Jörg refuses to do so because he refuses to understand the licenses, and expects every one else to agree with his highly irregular interpretation.

(Log in to post comments)

cdrtools - a tale of two licenses

Posted Aug 14, 2006 17:24 UTC (Mon) by AJWM (subscriber, #15888) [Link]

>The GPL requires that the necessary scripts used to build the work be made available under the same terms as the source

That only applies if "the work" is an executable. As an above poster pointed out, if you're just distributing a bunch of C source files, there are no scripts involved -- the work is what it is. As soon as somebody compiles that and distributes the binary, _then_ they have to pass on the source and build scripts too.

Debian's role

Posted Aug 14, 2006 19:53 UTC (Mon) by dark (subscriber, #8483) [Link]

Debian is in the "then" position -- it compiles binary packages and ships them, along with the source. If it can't do that in accordance with the terms of the license, then that package won't go into Debian.