<br><br><div><span class="gmail_quote">On 13/11/2007, <b class="gmail_sendername"><a href="mailto:salsaman@xs4all.nl">salsaman@xs4all.nl</a></b> <<a href="mailto:salsaman@xs4all.nl">salsaman@xs4all.nl</a>> wrote:</span>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">On Mon, November 12, 2007 22:13, John Winters wrote:<br>>> John Winters wrote:<br>>>> Say I've taken an existing GPLed package and modified it slightly to
<br>>>> give<br>>>> it an extra feature which you need. I haven't distributed the package<br>>>> yet<br>>>> so I am under no obligation to let you have either the binary or the<br>
>>> source. You ask me to sell you a copy and I say it'll cost you £1000.<br>>>> You counter that you haven't got £1000 so I offer it to you for five<br>>>> annual payments of £200.<br>
>><br>>> It depends in what way you sell it to them, no? If you send them a copy<br>>> of the software, you are distributing it, are you not? Therefore under<br>>> the terms of the GPL, you must make the source available on request, no?
<br>><br>> Yes, but that's not the point in question. I was describing a scenario in<br>> which someone could end up paying yearly instalments for piece of GPL<br>> software.<br>><br>> If you want to worry about when the source distribution happens then
<br>> assume I include it with the binaries, thus avoiding all problems.<br>><br>>> In this circumstance, I would assume the terms of the first licence the<br>>> software was put under, the GPL and not yours, would apply.
<br>><br>> There is only one licence in the scenario - the GPL. Because the original<br>> package was licensed to me under the GPL I can only pass on my modified<br>> version (if I choose to pass it on at all) under the same licence. I am
<br>> however free to ask whatever fee I like for giving you a copy (and you are<br>> free to choose not to pay it, but then I won't give you a copy of my<br>> modified package).<br>><br>> Once you've received your copy you can pass it on as you will, but you
<br>> still need to pay me the money which we agreed.<br>><br>> John<br>><br>> --<br>> Gllug mailing list - <a href="mailto:Gllug@gllug.org.uk">Gllug@gllug.org.uk</a><br>> <a href="http://lists.gllug.org.uk/mailman/listinfo/gllug">
http://lists.gllug.org.uk/mailman/listinfo/gllug</a><br>><br>><br><br><br>Yes, that`s alright. Under the GPL, you can charge what you like for<br>distributing binaries. What you may not do is to charge for distributing
<br>the source to those you have distributed the binary to (except for<br>reasonable costs for the media and postage if applicable). RMS himself has<br>stated that he has no objections to this.<br><br><br>Gabriel.<br><br>
</blockquote></div><br>Right so whats the "commercial" licence that you can buy on top of things like Qt exactly for then if its already free.....<br><br>I know that some of them offer value added features, but the basic commercial version of Qt actually has features missing that are available under the GPL version.....
<br><br>I guess the answer is going to be its a licence to write code that uses Qt that does not have the be GPL its self, but then I can write what ever I like with it anyway so long as a also GPL it but I can charge what I like for it.....
<br><br>Hense by buying a commercial licence for Qt you are buying the right to break the GPL which in theory you could be taken to court for so the Qt commercial licence is not a licence at all but an emunity from prosecution.
<br><br>Please do not try and explain licence law, and patient law its a doomed practice anyway...<br><br>Peter Childs<br>