On Wed, 2006-03-01 at 12:14 -0800, Tim Hill wrote:
> =Problem=
> Consider the drawing application OmniGraffle, which stores drawings in
> packages with an extension of ".graffle". Create a drawing and save it
> as "foo.graffle". Remember, this isn't a normal file: it's a directory
> that contains files, it just looks like a file in Finder.
>
> Add this drawing to an SVN repository. This works fine, *however* at
> this stage SVN creates its normal hidden ".svn" directory _inside_ the
> package, since as far as it is concerned, this is a normal directory,
> not a package.
>
> Now update the drawing in OmniGraffle and save it. One of three things
> will now happen depending upon the application:
>
> (3) The application creates a new temporary package, saves the updated
> drawing to that location, then deletes the old package and renames the
> new package to the final save name (foo.graffle). Most apps I'm aware of
> use this approach.
>
> Option (3) is the problem. A side-effect of saving the file in this way
> is the elimination of the ".svn" folder created by SVN. This, of course,
> confuses SVN no end when it comes to a later commit.
I've come to this thread a little late but I do have an alternative
solution: use SVK as your client instead of svn. SVK uses a different
working copy format that doesn't involve adding .svn directories to each
and every directory in the working copy. In fact it doesn't add anything
to the working copy: the working copy information is stored elsewhere.
Of course, this doesn't solve the general problem of using svn with Mac OS
X, but it is a potential solution to your specific problem.
--
Russ
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Mar 2 19:55:58 2006