LGPL license violation (Neon) on Windows

I was having a conversation with Brian Behlendorf (who was trying to
clear up some license question about Subversion he was getting). I
might as well share that part too. The Eclipse Foundation will not
let Subversion binaries be included in a distribution because it uses
an LGPL component (Neon). They cannot support LGPL because their
license allows the package to be relicensed commercially and LGPL does
not permit that. Anyway, I think Brian is going to let them know
about Serf.

In the process of going through this with Brian he looked at our
Windows download and said "I do not see Neon in this". I pointed out
that this is because we have always statically linked Neon on Windows.
 Brian pointed out that we cannot do this, it violates the terms of
the LGPL. If we are going to provide a binary distribution, then in
order to comply with the LGPL, Neon has to be compiled as a DLL in our
distribution.

Who understands the build system enough to make this change? In 1.5,
you currently get a libsvn_ra_dav.dll. This has ra_neon, ra_serf,
neon, serf and zlib all compiled on one library. It seems like we
might as well break up all of this and have separate libs for ra_neon
and ra_serf and provide Serf and Neon as DLL's.

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org