At 10:39 PM 2/4/2002 +0100, Branko =?UTF-8?B?xIxpYmVq?= wrote:
>Now really, this belongs to the Neon documentation. You should just point
>people to that. The last thing you want to do is update the docs for
>building neon every time a new version is released.
I take your point. If the versions required are specified by Neon, we then
have to track the Neon changes in our own documentation.
But the Subversion documentation should let the user know how to build
Subversion in all its variations. If I want to build a Subversion server
that supports SSL, I want to know about the --with-ssl option and what to
pass into it. The same if I want a server that supports compression. The
fact that these end up getting passed to the Neon build is completely
incidental to me. To the person building the system, Neon is just a black
box that Subversion uses to do its thing somehow.
What isn't incidental is the other libraries I have to have on my system so
that my Subversion server will have the feature I asked for. Now, Neon
probably defines what versions of these are required, making this a
dependency of a dependency. But I still need that information if I want to
build an SSL-capable Subversion server.
So although there is some overhead in doing so, I think it makes sense to
include that information in the INSTALL file.
>Thanks. The Win32 part of the docs is now committable. Again, someone else
>will have to bless the Unix part.
Thanks.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:37:04 2006