You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Bruce Atherton <br...@callenish.com> on 2002/02/14 08:42:05 UTC
[PATCH] Identify dependencies of dependencies in INSTALL
I've made the changes I talked about earlier concerning identifying the
optional dependent libraries of Neon, with some information about
Apache as well. Someone may wish to doublecheck that I have all the
details correct there.
I've tried to make the changes consistent with the things Brane was
asking for (redirecting to the other application's documentation for most
details) while still keeping the "recipe" format, ie. a list of ingredients
followed by step by step instructions. If you have any suggestions on
how to do it better, fire away and I'll do my best to fix it.
Log:
* INSTALL:
Added information to the build requirements about optional libraries
used by our dependents that can add functionality to Subversion.
Factored the same information out of the windows-specific section
since it is broadly applicable. Also cleaned up a couple of glitches
in text elsewhere.
Index: ./INSTALL
===================================================================
--- ./INSTALL
+++ ./.svn/tmp/INSTALL.63176.00001.tmp Thu Feb 14 00:02:39 2002
@@ -29,21 +29,21 @@
==================
Subversion depends on a number of third party tools and libraries.
- If you are bootstrapping from a tarball or an RPM then you will
- already have everything you require to get a Subversion client. So
- long as you don't plan to build a new client from the latest source
- or to build a Subversion server, you can go directly to section
- II.A.
+ If you are bootstrapping from a tarball, zipfile or an RPM then
+ you will already have everything you require to get a Subversion
+ client. So long as you don't plan to build a new client from the
+ latest source or to build a Subversion server, you can go directly
+ to section II.A.
Otherwise, you need to read the following so that you can determine
what other tools and libraries will be required so that Subversion
can be built with the set of features you want.
- The './configure' script will tell you if you are missing the
- correct version of any of the required libraries or tools, so if
- you are in a real hurry to get building, you can skip straight to
- section II. If you want to gather the pieces you will need before
- starting out, however, you should read the following.
+ On Unix systems, the './configure' script will tell you if you are
+ missing the correct version of any of the required libraries or
+ tools, so if you are in a real hurry to get building, you can skip
+ straight to section II. If you want to gather the pieces you will
+ need before starting out, however, you should read the following.
Note: Because previous builds of Subversion may have installed older
versions of these libraries, you may want to run some of the cleanup
@@ -167,20 +167,23 @@
repository, you don't need it.
You'll need Berkeley DB 4.0.14 installed on your system. You can
- get it from http://www.sleepycat.com/.
+ get it from:
+
+ http://www.sleepycat.com/.
If you already have another version of Berkeley DB installed and
don't want to downgrade, you can unpack the Berkeley 4.0.14
distribution into a subdir named `db' in the top-level of the
Subversion source tree. Then Subversion will ignore the system
DB and use the one it found in its own source tree.
+
Alternatively, you can add this flag
--with-berkeley-db=/usr/local/BerkeleyDB.4.0
to your `configure' switches, and the build process will use the
- named Berkeley. You may need to use a different path, of
- course.
+ Berkeley library in the named directory. You may need to use a
+ different path, of course.
If you are on the Windows platform and want to build Subversion,
a precompiled version of the Berkeley DB library is available for
@@ -239,6 +242,69 @@
the cygwin1.dll file into the same directory.
+ 11. Libraries for our libraries
+
+ Some of the libraries that Subversion depends on themselves have
+ optional dependencies that can add features to what Subversion
+ can do. Here are some examples.
+
+ The Neon library has support for SSL encryption by relying on the
+ OpenSSL library. When Neon is created with this dependency, then
+ the Subversion client inherits the ability to support SSL
+ connections. Neon also has support for sending compressed data
+ using the zlib library which a Subversion client can take
+ advantage of.
+
+ With Unix-based systems, you can enable this support from the
+ Subversion build provided that you are building Neon in the
+ "./neon/" directory as described above in section I.5. You also
+ need the OpenSSL and/or zlib library installed on your system,
+ depending on which features you want. Just add "--with-ssl" or
+ "--with-zlib" as parameters when you run Subversion's
+ "./configure", and they will be passed on to the Neon build
+ system. Consult the Neon documentation for more information on
+ how to use these parameters and versions of libraries you need.
+
+ Under Windows, you have to edit a batch file available in your
+ Subversion source tree (the root of which is labelled <SVN>
+ below):
+
+ <SVN>\build\win32\build_neon.bat
+
+ and point it to the appropriate directories.
+
+ You can also add support for these features to a Subversion server
+ and you can even use the same support libraries. The Subversion
+ build system will not provide them, however. You add them by
+ specifying parameters to the "./configure" script of the Apache
+ Server instead.
+
+ For getting SSL on your server, you would add the "--enable-ssl"
+ or "--with-ssl=/path/to/lib" option to Apache's "./configure"
+ script. Apache enables zlib support by default, but you can
+ specify a nonstandard location for the library with the
+ "--with-z=/path/to/dir" option. Consult the Apache documentation
+ for more details, and for other modules you may wish to install
+ to enhance your Subversion server.
+
+ If you don't already have it, you can get a copy of OpenSSL,
+ including instructions for building and packaging on both Unix
+ systems and Windows, at:
+
+ http://www.openssl.org/
+
+ Many Unix systems already come with zlib, but if you need it it
+ is available from:
+
+ http://www.gzip.org/zlib/
+
+ Windows users should just get the pre-built package:
+
+ http://www.gzip.org/zlib/contrib/zlib113-Win32.zip
+
+ The neon build scripts on Windows are set up to use those
+ libraries.
+
II. INSTALLATION
============
@@ -268,7 +334,7 @@
After compiling, you will have a large 'svn' binary sitting in
the tree. Use it to check out a real Subversion working copy:
- $ subversion-X.Y/subversion/clients/cmdline/svn checkout \
+ $ subversion-rXXXX/subversion/clients/cmdline/svn checkout \
http://svn.collab.net/repos/svn/trunk -d svn
A svn/dist.sh
@@ -468,13 +534,8 @@
supported at this time.
To build the client components, you'll need a copy of neon
- 0.18.5. The sources are available at
-
- http://www.webdav.org/neon/neon-0.18.5.tar.gz
-
- Unpack the distribution into the root directory of the Subversion
- source tree (henceforth know as <SVN> -- that's where you found
- this file) and rename the directory neon-0.18.5 to neon.
+ 0.18.5. See section I.5 for details on where to get one and what
+ to do with it when you get it.
[NOTE: The neon library supports secure connections with OpenSSL
and on-the-wire compression with zlib. If you want to use
@@ -484,29 +545,12 @@
to point to the appropriate directories.
- You can get a copy of OpenSSL, including instructions for
- building and packaging on Windows, at
-
- http://www.openssl.org/
-
- Zlib is available from
-
- http://www.gzip.org/zlib/
-
- but I recommend just using the pre-build package,
-
- http://www.gzip.org/zlib/contrib/zlib-Win32.zip
-
- The neon build scripts are set up to use those libraries.]
+ See Section I.11 for more details.
If you want to build the (local) server components, you'll also
- need a copy of Berkeley DB, version 4.0.14 or newer. The sources
- are available at
-
- http://www.sleepycat.com
-
- For your convenience, there is also a binary distibution on the
- Subversion downloads page
+ need a copy of Berkeley DB, version 4.0.14 or newer. Details are
+ in Section I.6. For your convenience, there is also a binary
+ distibution on the Subversion downloads page
http://subversion.tigris.org/ProjectDownloadList
@@ -599,6 +643,10 @@
This note assumes you have installed Berkeley DB 4.0.14
at its default locations. For more info about the db requirement,
see section I.6.
+
+ You may also want to include other modules in your build. Add
+ --enable-ssl to turn on SSL support, for example. Consult the
+ Apache documentation for more details.
All instructions below assume you configured Apache to install
under /usr/local/apache2/; substitute appropriately if you
Re: [PATCH] Identify dependencies of dependencies in INSTALL
Posted by Alan Shutko <at...@acm.org>.
cmpilato@collab.net writes:
> Bruce Atherton <br...@callenish.com> writes:
>
>> At 11:11 AM 2/15/2002 -0600, cmpilato@collab.net wrote:
>> >A note, though, Bruce. As if there aren't enough things to remember
>> >when trying to maintain consistency while editing, please additionally
>> >note that files like INSTALL use two spaces between the end of a
>> >sentence and the beginning of the next.
[...]
>> Perhaps it should be added to HACKING? Is that rule consistent
>> across all documentation, including comments, log messages, etc?
>
> Hmm...without trying to sound like a big meany, I think that rule is
> written in every American English grammar book currently in print.
Doubtful, because it's not a grammar rule, it's typographical, and in
fact it's not a rule in real typography, but a convention used in
typewritten manuscripts in the US (maybe in some other countries too,
but not all). Which are quite similar to monospaced text files, so if
one wants to use the rule that's ok, but it's not universal.
--
Alan Shutko <at...@acm.org> - In a variety of flavors!
One seldom sees a monument to a committee.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [PATCH] Identify dependencies of dependencies in INSTALL
Posted by Karl Fogel <kf...@newton.ch.collab.net>.
Bruce Atherton <br...@callenish.com> writes:
> Up to you guys. I was just trying to save you work cleaning up
> submissions from people like me.
Well, let's put it this way: I'll certainly appreciate it if there are
two spaces (since M-a and M-e will work, and it will be easier for me
to read). But I'll never reject a patch because of it, nor would
anyone else afaik.
-K
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [PATCH] Identify dependencies of dependencies in INSTALL
Posted by Bruce Atherton <br...@callenish.com>.
At 01:06 PM 2/15/2002 -0600, Karl Fogel wrote:
>I wanted to avoid joining this thread, but I see I can't, heh:
Sorry to drag you in.
>Certainly, let's keep leave it to the contributor's discretion,
>though. I mean, do we really need a convention about the number of
>spaces after a period? :-)
Up to you guys. I was just trying to save you work cleaning up submissions
from people like me.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [PATCH] Identify dependencies of dependencies in INSTALL
Posted by Karl Fogel <kf...@newton.ch.collab.net>.
Karl Fogel <kf...@newton.ch.collab.net> writes:
> No, and we don't have one (see HACKING).
>
> (The reason for *maintaining* a given style if you find it in code is
> to make life easier for whoever apparently works most often in that
> code; i.e., it's a courtesy.)
Sorry, that sounded all harsh (to my virtual ears, anyway).
All I really meant to say is, I'm not going to worry too much if a
patch doesn't have the two spaces after a period. After applying, I
might say "I changed all your periods thusly...", that's all.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [PATCH] Identify dependencies of dependencies in INSTALL
Posted by Karl Fogel <kf...@newton.ch.collab.net>.
cmpilato@collab.net writes:
> Do we really need a convention about the presence of a space between
> the function name and the opening paren? Certainly doesn't affect the
> compiler's ability to generate binaries.
No, and we don't have one (see HACKING).
(The reason for *maintaining* a given style if you find it in code is
to make life easier for whoever apparently works most often in that
code; i.e., it's a courtesy.)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [PATCH] Identify dependencies of dependencies in INSTALL
Posted by cm...@collab.net.
Karl Fogel <kf...@newton.ch.collab.net> writes:
> Certainly, let's keep leave it to the contributor's discretion,
> though. I mean, do we really need a convention about the number of
> spaces after a period? :-)
Do we really need a convention about the presence of a space between
the function name and the opening paren? Certainly doesn't affect the
compiler's ability to generate binaries.
Look, I don't honestly care about the formatting rules and regulations
across the board for our code, (so long as readability is of the
highest priority), but there's no reason why we shouldn't expect
contributions to at least maintain the consistency of the files they
are patching. Oh, that's right, we already *do* expect that of the
patches ... unless there's some magical difference between source code
and prose that I'm overlooking. text/plain to me all the same.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [PATCH] Identify dependencies of dependencies in INSTALL
Posted by Karl Fogel <kf...@newton.ch.collab.net>.
Bruce Atherton <br...@callenish.com> writes:
> Seriously, it used to be the standard but has long since been
> supplanted with a single period, thanks in large part to
> proportionally-spaced fonts. In fact, if your HTML has two spaces
> after a period it will still be shown as a single space by any browser
> (as a "feature" of HTML parsing). I know that I have become habituated
> to putting in only one space.
>
> However, since plain text files are almost certainly displayed fixed
> width, it makes a lot of sense to go back to that old standard for all
> our documentation. How many use a text editor with a proportionally
> spaced font? Or an xterm? So the rule makes sense, but I don't think
> you could say it was obvious. Not to me, anyway.
I wanted to avoid joining this thread, but I see I can't, heh:
Some editors' sentence-motion commands depend on that extra space (see
Mike's example of an ambiguous sentence-end for why). Personally I
also find it helps readability, but the main thing is that Emacs M-a
and M-e work when there are two spaces. Possibly other editors do
too, I don't know.
Certainly, let's keep leave it to the contributor's discretion,
though. I mean, do we really need a convention about the number of
spaces after a period? :-)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [PATCH] Identify dependencies of dependencies in INSTALL
Posted by cm...@collab.net.
Bruce Atherton <br...@callenish.com> writes:
> At 12:24 PM 2/15/2002 -0600, cmpilato@collab.net wrote:
> >Hmm...without trying to sound like a big meany, I think that rule is
> >written in every American English grammar book currently in print.
>
> <*Sniff*> Oh, that's ok. I'll get over it. Eventually.
>
> Seriously, it used to be the standard but has long since been supplanted
> with a single period, thanks in large part to proportionally-spaced fonts.
> In fact, if your HTML has two spaces after a period it will still be shown
> as a single space by any browser (as a "feature" of HTML parsing). I know
> that I have become habituated to putting in only one space.
>
> However, since plain text files are almost certainly displayed fixed width,
> it makes a lot of sense to go back to that old standard for all our
> documentation. How many use a text editor with a proportionally spaced
> font? Or an xterm? So the rule makes sense, but I don't think you could say
> it was obvious. Not to me, anyway.
You're absoletely right. Apologies where required/requested and all
that stuff. :-)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [PATCH] Identify dependencies of dependencies in INSTALL
Posted by Bruce Atherton <br...@callenish.com>.
At 12:24 PM 2/15/2002 -0600, cmpilato@collab.net wrote:
>Hmm...without trying to sound like a big meany, I think that rule is
>written in every American English grammar book currently in print.
<*Sniff*> Oh, that's ok. I'll get over it. Eventually.
Seriously, it used to be the standard but has long since been supplanted
with a single period, thanks in large part to proportionally-spaced fonts.
In fact, if your HTML has two spaces after a period it will still be shown
as a single space by any browser (as a "feature" of HTML parsing). I know
that I have become habituated to putting in only one space.
However, since plain text files are almost certainly displayed fixed width,
it makes a lot of sense to go back to that old standard for all our
documentation. How many use a text editor with a proportionally spaced
font? Or an xterm? So the rule makes sense, but I don't think you could say
it was obvious. Not to me, anyway.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [PATCH] Identify dependencies of dependencies in INSTALL
Posted by cm...@collab.net.
"Sander Striker" <st...@apache.org> writes:
> > Hmm...without trying to sound like a big meany, I think that rule is
> > written in every American English grammar book currently in print.
> >
> > *shrug*
>
> The only thing is, is that we are not all americans...
Oh, of course not. Some of us aren't even human. {grins wickedly}
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
RE: [PATCH] Identify dependencies of dependencies in INSTALL
Posted by Sander Striker <st...@apache.org>.
> From: cmpilato@collab.net [mailto:cmpilato@collab.net]
> Sent: 15 February 2002 19:24
> Bruce Atherton <br...@callenish.com> writes:
>
> > At 11:11 AM 2/15/2002 -0600, cmpilato@collab.net wrote:
> > >A note, though, Bruce. As if there aren't enough things to remember
> > >when trying to maintain consistency while editing, please additionally
> > >note that files like INSTALL use two spaces between the end of a
> > >sentence and the beginning of the next.
> >
> > I hadn't realized that. Thanks for the information, and sorry for the added
> > work.
>
> Oh, no problem.
>
> > Perhaps it should be added to HACKING? Is that rule consistent
> > across all documentation, including comments, log messages, etc?
>
> Hmm...without trying to sound like a big meany, I think that rule is
> written in every American English grammar book currently in print.
>
> *shrug*
The only thing is, is that we are not all americans...
Sander
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [PATCH] Identify dependencies of dependencies in INSTALL
Posted by Colin Putney <cp...@whistler.net>.
On Friday, February 15, 2002, at 10:24 AM, cmpilato@collab.net wrote:
> Bruce Atherton <br...@callenish.com> writes:
>
>> At 11:11 AM 2/15/2002 -0600, cmpilato@collab.net wrote:
>>> A note, though, Bruce. As if there aren't enough things to remember
>>> when trying to maintain consistency while editing, please additionally
>>> note that files like INSTALL use two spaces between the end of a
>>> sentence and the beginning of the next.
>>
>> I hadn't realized that. Thanks for the information, and sorry for the
>> added
>> work.
>
> Oh, no problem.
>
>> Perhaps it should be added to HACKING? Is that rule consistent
>> across all documentation, including comments, log messages, etc?
>
> Hmm...without trying to sound like a big meany, I think that rule is
> written in every American English grammar book currently in print.
>
> *shrug*
Not so. This is actually a typesetting issue. The practice arose because
typewriters use mono-space fonts and periods end up having too much
white space around them, which makes it visually more difficult to see
the end of sentences. Using two spaces after a period is a essentially a
hack to correct this problem and is unnecessary with variable-width
fonts. Unfortunately typewriters have been in use for about a hundred
years, much longer than laser printers, and the practice quite
enshrined.
*shrug* :-)
- Colin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [PATCH] Identify dependencies of dependencies in INSTALL
Posted by cm...@collab.net.
Bruce Atherton <br...@callenish.com> writes:
> At 11:11 AM 2/15/2002 -0600, cmpilato@collab.net wrote:
> >A note, though, Bruce. As if there aren't enough things to remember
> >when trying to maintain consistency while editing, please additionally
> >note that files like INSTALL use two spaces between the end of a
> >sentence and the beginning of the next.
>
> I hadn't realized that. Thanks for the information, and sorry for the added
> work.
Oh, no problem.
> Perhaps it should be added to HACKING? Is that rule consistent
> across all documentation, including comments, log messages, etc?
Hmm...without trying to sound like a big meany, I think that rule is
written in every American English grammar book currently in print.
*shrug*
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [PATCH] Identify dependencies of dependencies in INSTALL
Posted by Bruce Atherton <br...@callenish.com>.
At 11:11 AM 2/15/2002 -0600, cmpilato@collab.net wrote:
>A note, though, Bruce. As if there aren't enough things to remember
>when trying to maintain consistency while editing, please additionally
>note that files like INSTALL use two spaces between the end of a
>sentence and the beginning of the next.
I hadn't realized that. Thanks for the information, and sorry for the added
work.
Perhaps it should be added to HACKING? Is that rule consistent across all
documentation, including comments, log messages, etc?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [PATCH] Identify dependencies of dependencies in INSTALL
Posted by cm...@collab.net.
Bruce Atherton <br...@callenish.com> writes:
> You are absolutely right, I should have checked into that more. The
> fix follows.
>
> >> + http://www.gzip.org/zlib/contrib/zlib113-Win32.zip
> >
> >This URL gets a 404.
's alright. I fixed this already.
> Log:
>
> * INSTALL
> Correct an error that claimed Neon requires a parameter to support
> compression. In fact, it is enabled by default.
Committed.
A note, though, Bruce. As if there aren't enough things to remember
when trying to maintain consistency while editing, please additionally
note that files like INSTALL use two spaces between the end of a
sentence and the beginning of the next. I know, I know, it sounds
really picky. But it's the difference between:
He was picking on J. C. Penney didn't really like that.
and:
He was picking on J. C. Penney didn't really like that.
^^^^^^^^^^^^
Who was he picking on? J.? J.C.? J.C.Penney? You get the point.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [PATCH] Identify dependencies of dependencies in INSTALL
Posted by Bruce Atherton <br...@callenish.com>.
At 01:17 PM 2/14/2002 -0800, Blair Zajac wrote:
>Do you need to add --with-zlib? I think it picks up zlib support by
>default, however it needs to be told about OpenSSL support.
You are absolutely right, I should have checked into that more. The
fix follows.
>> + http://www.gzip.org/zlib/contrib/zlib113-Win32.zip
>
>This URL gets a 404.
Ain't that always the way. You correct one error (the URL now
requires a version number) but miss another (capitalization).
And as we all know, testing fixes is for wimps.
Thanks for catching it. I see a fix for this has already been applied.
Log:
* INSTALL
Correct an error that claimed Neon requires a parameter to support
compression. In fact, it is enabled by default.
Index: ./INSTALL
===================================================================
--- ./INSTALL
+++ ./.svn/tmp/INSTALL.63320.00001.tmp Thu Feb 14 15:27:49 2002
@@ -255,15 +255,18 @@
using the zlib library which a Subversion client can take
advantage of.
- With Unix-based systems, you can enable this support from the
+ With Unix-based systems, you can enable support for SSL from the
Subversion build provided that you are building Neon in the
"./neon/" directory as described above in section I.5. You also
- need the OpenSSL and/or zlib library installed on your system,
- depending on which features you want. Just add "--with-ssl" or
- "--with-zlib" as parameters when you run Subversion's
- "./configure", and they will be passed on to the Neon build
- system. Consult the Neon documentation for more information on
- how to use these parameters and versions of libraries you need.
+ need OpenSSL installed on your system. Just add "--with-ssl" as
+ a parameter when you run Subversion's "./configure", and it will
+ be passed on to the Neon build system. If your OpenSSL
+ installation is hard for Neon to find, you may need to use
+ "--with-ssl=/path/to/lib" instead. The zlib library is included
+ in Neon by default, but you can also specify a path to the
+ library using "--with-zlib". Consult the Neon documentation for
+ more information on how to use these parameters and versions of
+ libraries you need.
Under Windows, you have to edit a batch file available in your
Subversion source tree (the root of which is labelled <SVN>
Re: [PATCH] Identify dependencies of dependencies in INSTALL
Posted by Blair Zajac <bl...@orcaware.com>.
Bruce Atherton wrote:
> + With Unix-based systems, you can enable this support from the
> + Subversion build provided that you are building Neon in the
> + "./neon/" directory as described above in section I.5. You also
> + need the OpenSSL and/or zlib library installed on your system,
> + depending on which features you want. Just add "--with-ssl" or
> + "--with-zlib" as parameters when you run Subversion's
> + "./configure", and they will be passed on to the Neon build
> + system. Consult the Neon documentation for more information on
> + how to use these parameters and versions of libraries you need.
> +
Do you need to add --with-zlib? I think it picks up zlib support by
default, however it needs to be told about OpenSSL support.
> + Windows users should just get the pre-built package:
> +
> + http://www.gzip.org/zlib/contrib/zlib113-Win32.zip
This URL gets a 404.
Best,
Blair
--
Blair Zajac <bl...@orcaware.com>
Web and OS performance plots - http://www.orcaware.com/orca/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org