Mercurial > hgsubversion
view tests/fixtures/executebit.sh @ 611:b70f7c82b9b8
svncommands: fix layering violation & tweak error messages.
Importing `SubversionException' directly from `svn.core' is a layering
violation: Anything within the Subversion bindings should only be
accessed via svnwrap.
The advantages to doing this are twofold: we only need to intercept
missing bindings in one place, and we have the option of supporting
alternate bindings. As an added bonus, the recently-added support for
intercepting missing Subversion bindings actually works.
Two error messages are tweaked to remove `It appears...' from one
error message (just blaming Subversion instead) and make both errors
include the URL in the suggested command line.
author | Dan Villiom Podlaski Christiansen <danchr@gmail.com> |
---|---|
date | Fri, 14 May 2010 20:22:32 +0200 |
parents | c35f59aa200e |
children |
line wrap: on
line source
#!/bin/sh # # Generate executebit.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 echo text > text1 echo text > text2 touch empty1 touch empty2 python -c "file('binary1', 'wb').write('a\x00b')" python -c "file('binary2', 'wb').write('a\x00b')" svn add text1 text2 binary1 binary2 empty1 empty2 svn propset svn:mime-type application/octet-stream binary1 binary2 svn propset svn:executable yes binary1 text1 empty1 svn ci -m init # switch exec properties svn propdel svn:executable binary1 text1 empty1 svn propset svn:executable yes binary2 text2 empty2 svn ci -m changeexec cd ../.. svnadmin dump testrepo > ../executebit.svndump