Toby Johnson wrote:
> Stefan Küng wrote:
>
>> With that exception clause, we just can say that *other* people can
>> still link TSVN with the required libraries. But strictly speaking
>> we're not allowed to link TSVN and ship it that way. That would make
>> TSVN a source-only distribution, without an installer.
>
>
> I don't think this is true. A body of work comes under the GPL when the
> developer(s) release it that way, and not before. See this section if
> you hadn't before:
> <http://www.gnu.org/licenses/gpl-faq.html#DeveloperViolate>
>
> "The developer itself is not bound by [the GPL], so no matter what the
> developer does, this is not a 'violation' of the GPL." Straight outta
> the horse's mouth.
>
> The only way I see you could run afoul of this is if you somehow took
> two libraries, one GPL and one GPL-incompatible, linked them together
> (in violation of the GPLed library's terms), and then used that
> intermediate object in TSVN.
Yep. That all makes sense, thanks for providing the clarifications. The
GPL avoids legal jargon quite successfully, but it's not always
completely clear what you can and can't do. Playing 'spot the
difference' with the multitude of free/open source licenses was driving
me nuts yesterday.
> And for what it's worth, you can use the
> Perl-syntax-parsing regex I submitted under whichever license you wish. :)
Thanks.
Simon
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Fri Aug 19 19:02:10 2005