Max Bowsher wrote:
>Jens Peters wrote:
>
>
>>I know that you don't want this kind of questions, and don't want to ask
>>this too, but just to be sure:
>>
>>I recently updated my server (official subversion via apache) to version
>>1.0.6 without any problems. If I replace the binaries with the
>>unsupported version from branko (_svn), do I have to except any changes
>>on the server components (thus mod_*.so, svnadmin.exe etc., thus all
>>files except svn.exe) and do I have to except some incompatabilties with
>>my db-files? I guess the answer is no, but since the unsupported package
>>includes all binaries and not just svn.exe I'm a little bit unsure.
>>
>>
>
>DB files will be compatible, but it is a bad idea to mix different binary
>distributions of subversion. There are several different C runtime library
>versions on Windows, and having some svn dlls/exes using one and other
>dlls/exes using another could cause subtle and obscure problems.
>
>
Well, I build both distros with the same dependencies, and the SVN
libraries aren't shared on Windows (yet), so those problems don't exist.
>(Oh, and just replacing svn.exe will *NOT* work)
>
>
In fact, it will, for the reasons stated above. Of course, if you use
svnversion, you'll have to replace it too since it inspects the WC. And
the Python bindings are also affected, obviously, which is why they're
the only other component that I rebuild with the ASP.NET bug workaround.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jul 29 00:08:57 2004