G'day,
I've run into several people recently, both online and in real life, who
are daunted by the task of manually walking Subversion's build-time
dependency tree in order to build it from source on various UNIXes.
Several of them gave up on the task mid-way, and as a result were unable
to evaluate Subversion for their version control needs, which is sad. I
would like to help these people. If they're not willing/able to build SVN
from source, then the next best thing IMO is to give them pre-compiled
binaries.
(So in passing, here is a plea to the developers to try to keep the
dependency tree as small and as 'light' as possible. Pretty please, from
all of the semi-competent sysadmins out there).
I know about the binaries linked from
http://subversion.tigris.org/project_packages.html
but conspicuously absent from there are Tru64, HP-UX, AIX and SCO.
If I put on the Web a whole bunch of .tar.gzs or HP-UX depots or
AIX 5 RPMs or whatever containing Subversion binaries and their open
source shared library dependencies for various platforms, what are my
legal obligations?
As far as I can tell, all I have to do is link to the source code
corresponding to those binaries, plus also supply the one-line patch I
had to apply on HP-UX, plus note clearly that that version has been
modified by that one-line patch. This seems to satisfy the Apache, neon,
BDB and OpenSSL licenses.
Anyone know different/better than this? IANAL.
Cheers,
--matt
Matthew Sanderson
Senior Programmer (UNIX)
TCG Information Systems Pty Ltd
Sydney, Australia
matthew@formtrap.com
http://www.formtrap.com/
+61 (02) 8303 2407
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Dec 8 05:27:09 2005