On 9/1/05, Erik Huelsmann <ehuels@gmail.com> wrote:
> Ok. this issue came up while discussing the merits of ripping out neon
> and APR out of the source tree.
>
> I'm definitely not opposed to providing an archive which contains
> sources of our dependencies, but the question is: how do we maintain
> it and which dependencies do we include and which ones not?
My rule of thumb: If the software is required to use the basic
functionality of the Subversion client, we should include it (unless
the license is troublesome).
> To include at a minimum:
> - APR
> - Neon
>
> Optional:
> - Zlib
Zlib is handy. Let's include it.
> - OpenSSL (only by reference to the openssl site?)
SSL support is an important client-side feature. We can include
OpenSSL directly in our "Subversion Dependencies" package, as long as
our dependencies tarball contains the following acknowledgements:
- This product includes software developed by the OpenSSL project for
use in the OpenSSL Toolkit (http://www.openssl.org/)
- This product includes cryptographic software written by Eric Young
(eay@cryptsoft.com)
- This product includes software written by Tim Hudson (tjh@cryptsoft.com)
I think it's fine to put those acknowledgements in our "dependency tarball".
> - libxml2 / expat (included in the APR source distro?)
libxml2 / expat is optional, right?
> - BDB (only by reference to the sleepycat site?)
> - gettext
BDB has a restrictive license which may cause headaches for us. I'd
say, include it only by reference. The same applies to "gettext".
> - Apache2
Definitely not. This would be going too far :)
--
David James -- http://www.cs.toronto.edu/~james
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Sep 1 15:54:00 2005