David Chapman <dcchap...@acm.org> writes: > On 1/25/2016 10:45 AM, Philip Martin wrote: >> It should just work for both repositories and working copies. > > Is that documented somewhere, such that system administrators can rely > on it?
I don't know if it is explictly documented anywhere. The closest I can get is: http://svnbook.red-bean.com/nightly/en/svn.reposadmin.planning.html#svn.reposadmin.basics.backends.tbl-1 > Or could a Subversion developer decide to put endian- or > size-dependent binary data into a repository or working copy file > somewhere? It happens but should be removed, for an example see http://svn.apache.org/r1573371 > My notes are vague, unfortunately. This was back in 2007, when I was > compiling from tarballs: > > 1) configure/compile with BDB support on both platforms > 2) copy repository directory to 32-bit machine > 3) problem found -> dump/load to avoid system dependencies > 4) problem solved > 5) hey, my repositories are actually FSFS! The BDB data files are portable but the BDB environment files are platform dependent. Switching platforms for BDB generally requires a BDB recover operation to replace the BDB environment files, and may require a BDB upgrade operation if the BDB library version changes. FSFS repositories need no special operations. -- Philip Martin WANdisco
