First off: apologies for not continuing the previous thread on this subject
but I couldn't remember it's title or find it on gmane.
Last night, I tried an experiment on a clean(ish) Server 2003 system. By
clean(ish), I mean that it had IIS disabled, and had never previously had
Apache, Subversion, TortoiseSVN, or Berkley DB installed on it. Hopefully
this should provide some evidence for this problem.
First I installed Apache 2.0.52. No problem. The Apache service was
installed and it was running fine. Then I installed Subversion. I disabled
the installer options for the documentation icons but left the Apache
configuration option enabled. The result was that the Apache service was
removed entirely and I had to execute apache -k install to reinstall it.
When I tried to restart the service, it failed because the intl.dll file was
not copied to the Apache2\modules directory.
Feel free to shoot me down for this suggestion but, wouldn't it be better to
install the contents of Subversion\httpd into Subversion\bin with all the
other binaries, and then configure Apache to load the .so modules from
Subversion\bin rather than its own Apache2\modules directory? That would
result in fewer copies of dynamically linked libraries spread around the
system and would also make Jostein's job of keeping the installer up-to-date
a little easier.
TTFN,
Damian.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Nov 5 11:31:09 2004