Revive svn+http(s) URLs support (issue94) Telling svn from mercurial repository automatically is not always possible, or at least not seamlessly. Let 'http://repo.com/svn' be an svn repository, protected with basic authentication. Trying to clone it directly does something like: 1- Open it like a mercurial repository: * send between command, ask for credentials, fail * fallback to static-http, ask for crendentials two times, fail 2- Open it like an svn repository Mercurial [auth] facility is helpful here, but few people know about it, and it may seem weird to store svn credentials in mercurial configuration. An svn-like password manager would not help either because all connections attempts in [1] fail and it's unlikely we would store credentials in this situation. Instead, we can clone 'svn+http://repo.com/svn', which will skip step [1].

#!/bin/sh
#
# Generate binaryfiles.svndump
#

mkdir temp
cd temp

mkdir project-orig
cd project-orig
mkdir trunk
cd ..

svnadmin create testrepo
svnurl=file://`pwd`/testrepo
svn import project-orig $svnurl -m "init project"

svn co $svnurl project
cd project/trunk
# Add a regular binary file, and an unflagged one
python -c "file('binary1', 'wb').write('a\0\0\nb\0b')"
python -c "file('binary2', 'wb').write('b\0\0\nc\0d')"
svn add binary1 binary2
svn propset svn:mime-type application/octet-stream binary1
svn propdel svn:mime-type binary2
svn ci -m 'add binaries'
# Update them
python -c "file('binary1', 'wb').write('a\0\0\nc\0d')"
python -c "file('binary2', 'wb').write('b\0\0\0\nd\0e')"
svn ci -m 'change binaries'
# Remove them
svn rm binary1 binary2
svn ci -m 'remove binaries'
cd ../..

svnadmin dump testrepo > ../binaryfiles.svndump