I keep everything I can in Subversion; it's one of the practices of a successful programmer. The Mac, though, makes things a bit tricky: Mac OS X bundles are in an ambiguous space between files and directories. To Subversion, they are directories whose contents are individually managed. That means .svn folders everywhere. To Mac applications, they are single files, to be rewritten at will (wiping out all those critical .svn folders). My approach has been to archive the bundle and check in the archive, marking the bundle itself as svn:ignore.
Doing this manually is a challenge, especially because you only want to re-archive a bundle if the contents of the bundle folder have changed. My solution uses a Ruby script to find bundles that need archiving and then invokes tar to do the actual work. More details are available in this entry on my blog.
[robg adds: I've mirrored the script here on macosxhints, but you should check the original posting for any updates. I have not tested this one.]
Doing this manually is a challenge, especially because you only want to re-archive a bundle if the contents of the bundle folder have changed. My solution uses a Ruby script to find bundles that need archiving and then invokes tar to do the actual work. More details are available in this entry on my blog.
[robg adds: I've mirrored the script here on macosxhints, but you should check the original posting for any updates. I have not tested this one.]
•
[5,416 views]

