I just tried to add my I7 projects directory to my personal svn repository. It looked like everything went okay, but now I’m having a weird problem:
$ svn ci
svn: Working copy '/Users/mike/eyeballsun/i' locked
svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for details)
$ svn cleanup
svn: 'headache.inform/Build' is not a working copy directory
What it looks like is that instead of just updating files within the Build and Source directory of a project, the IDE is completely replacing those directories, including the .svn subdirectories that Subversion uses to keep track of them. This could be a really nasty situation.
Has anyone actually managed to keep their I7 work in Subversion? Got any tricks for me?
Yeah, that’s exactly what’s happening. What I’m doing right now is that I run a script that copies the relevant files to another folder before submitting that folder to SVN. It’s one extra step but on the other hand at the same time I have the script to do other stuff like copy the relevant extensions to the same folder to be stored in the repository with the source code.
I’m wondering - The svn repository has hooks so you can do various things on the server before and after committing. But does the svn client have any hooks so you can do anything with the working directory before committing or checking out (like copying your Inform files into your working directory?)