view tests/fixtures/binaryfiles.sh @ 777:60948939555d

clone: pass on the repository instance rather than the string given Previously, cloning a Mercurial repository that required authentication would prompt for authentication twice. This is because hgclonewrapper() first created a repository instance, but didn't pass it on. hg.close() would then create another instance, and since Mercurial doesn't cache authentication credentials across instances, this would cause a second credential prompt. This change could have unfortunate side effects in case of other extensions wanting to modify the source passed to clone. This seems like a somewhat unlikely scenario. I'll think about a possible way to avoid all this hackery...
author Dan Villiom Podlaski Christiansen <danchr@gmail.com>
date Tue, 14 Dec 2010 12:09:27 +0100
parents f1919e1c35bf
children
line wrap: on
line source

#!/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