Quoting Ross N. Williams:
> Half true. Your library can be released under several licences including
> the GPL. That's how commercial vendors can release their code under the
> GPL and sell the same code as commercial products.
This is the key idea here. You don't license the _software_
so much as you license a _release_ of the software. You as the author
have complete control over the code. It's just that the license
defines the terms by which a user receives the software.
--
((lambda (x) (list x (list (quote quote) x)))
(quote (lambda (x) (list x (list (quote quote) x)))))
-- A LISP quine written by Seth David Schoen
+++ath
- Re: Does a GPL API infect its apps? Raymond Luk
- Re: Does a GPL API infect its apps? J.H.M. Dassen (Ray)
- Re: Does a GPL API infect its apps? Andrew J Bromage
- Re: Does a GPL API infect its apps? John Cowan
- Re: Does a GPL API infect its apps? Arandir
- Re: Does a GPL API infect its apps? John Cowan
- Re: Does a GPL API infect its apps? Ross N. Williams
- Re: Does a GPL API infect its apps? Arandir
- Re: Does a GPL API infect its apps? Ross N. Williams
- Re: Does a GPL API infect its apps? Nick Moffitt
- Re: Does a GPL API infect its apps? Ken Arromdee
- Re: Does a GPL API infect its apps? Ken Arromdee
- Re: Does a GPL API infect its apps? John Cowan
- Re: Does a GPL API infect its apps? Ken Arromdee
- Re: Does a GPL API infect its apps? John Cowan
- Re: Does a GPL API infect its apps? Ken Arromdee
- Re: Does a GPL API infect its apps? Ross N. Williams
- Re: Does a GPL API infect its apps? Ken Arromdee

