[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: AW: AW: AW: Crash of TortoiseSVN on Vista Ultimate x64, German localization

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: 2007-12-02 09:43:11 CET

Sabine Gehlen wrote:
> Stefan,
>
> Just to clarify:
>
> For a Berkley DB generated with TortoiseSVN x64 (or an x64 OS? ¹) I need
> TortoiseSVN x64 and I can't use svnserve or Apache (because they are x86).
> For a Berkley DB generated with TortoiseSVN x86 I can use svnserve or Apache
> and can access via TortoiseSVN x86 or x64.

Yes, almost. It has nothing to do with the OS you're using, just the
client and how it was compiled. The berkeley db isn't really compatible
between different setups: for example, even for the TSVN 32-bit build we
have to jump through some hoops to keep it compatible with the official
svn command line client since that one is built with VC6 and TSVN is
built with VS2005/VS2008. The reason is that the berkeley db doesn't
define their data structures in fixed length but uses the compiler
defines (which can change in size, for example the time_t structure is
now 64-bit, but was 32-bit for VC6).
We *may* be able to keep even the x64 build compatible, but that would
mean we'd have to override too many of the compiler defines - the risk
of breaking something important is IMHO too high...

As a rule of thumb, I'd say that you should access the repository only
with the same client you created it (or use the FSFS repository format).

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Sun Dec 2 09:43:31 2007

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.