[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: LGPL license violation (Neon) on Windows

From: Greg Hudson <ghudson_at_MIT.EDU>
Date: Fri, 09 May 2008 13:44:51 -0400

On Fri, 2008-05-09 at 13:34 -0400, Mark Phippard wrote:
> What about downstream? Does Subclipse, TortoiseSVN, AnkhSVN etc. need
> to provide the Subversion and Neon source code too?

Without doing research, I don't know if these people are providing
Subversion binary materials. If they're not embedding Subversion
binaries in what they distribute, they are pretty much off the hook. If
they are embedding them, then:

If they provide neon binaries, they need to provide neon source. We
can't eliminate that requirement as long as we're using neon.

If they provide neon binaries statically linked against Subversion
source code, they also need to provide Subversion linkable objects or
Subversion source code. Linking dynamically against neon in our Windows
build system might eliminate that issue, if the downstream distributor
is using our Windows build system or its products.

To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-05-12 05:46:05 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.