I’ve had a lot of people asking about dealing with bundles in ZigVersion, and so I scripted up what I had been doing to bundles manually. All I’m doing is re-writing all the .svn directories and adding/deleting files as necessary so that people don’t have to run the svn commands by hand; it creates a tarball on the local system to backup the files, since this script isn’t terribly well tested yet. It should end up checking in exactly what you would expect; no interim formats in the repisotory like a tar wrapper solution.

Of course, this was just a test script to help people out temporarily - the next step would be to integrate what it does (not the script itself) into ZigVersion, watching for the svn:opaque (or whatever) property, and doing the right stuff. Basically, acting exactly like what was suggested in the “opaque collections” issue, but deemed too hard or unimportant or whatever finally happened. I’m not to the point of adding it to ZigVersion yet (haven’t even decided this is the right thing to do), and I was going to bounce it around the subversion dev list first to see what kind of feedback I get on it; I guess someone caught wind of it sooner than I expected. Theoretically, this would work *exactly* like implementing it in the svn lib would work (assuming a hack that doesn’t require a new working copy format), and if it ends up getting into the svn lib in the future, should be a transparent upgrade. The solution isn’t

The right thing to do seems to be to throw out the way the working copy currently stores stuff (.svn), and do something else. I’ve toyed with the idea of supporting svk (in addition to svn) in some future version of ZigVersion in order to have the meta data stored outside of the direct filesystem (amongst other features); perhaps instead of doing what my test script does. But the script I put together solves a problem that lots of people are having right now; hopefully it ends up saving lots of people time and headaches trying to use subversion with bundles on macs.

It seems it is very much perceived as a Mac-only thing, hence the lack of action. The only workarounds have been for well-behaved apps on the Mac side to be careful about Subversion metadata inside bundles in the working copy. Interface Builder is an example of a well-behaved application. TextEdit is an example of a poorly-behaved one. But clearly having support for opaque collections in Subversion would be better than trying to modify every single program that ever works with bundle-based documents.