>>Your lather-rinse-repeat method is fine for one or two files, but the
>>workaround starts to make sense if you've got 100 obstructions...
>>
>>
>
>Actually, the part of Brandon's description that I found interesting
>is this part:
>
> The biggest problem that this creates is if you are storing lots of
> binaries in the repository and they are created via some sort of
> tool that generates lots of files. Artist Alex starts some initial
> work in the tool on one section of and fills up his working copy
> with these generated binaries. Artist Bob does the same thing, but
> because he's working in a different area but with the same tool, it
> generates lots of the same binaries.
>
>So, I have to ask, "Why are you versioning tool-generated binary
>files?" I'm trusting that there is a some good reason for these files
>to be versioned, but am admittedly interested in what those reasons
>might be. Educate me! :-)
>
>
Main reason: proprietary tools with either no source code or time to
fix them that store their data in a multi-file binary format.
In our case, the tools in question can do merges between the binary
files, but when you write out the resulting work to the disk, it stores
the work as several small binary pieces because these pieces can be
shared among several assets.
A similar case that you might have seen is when you use Dreamweaver edit
web pages. You have the current asset you are working on, which in
Dreamweaver's case is text/html. A side effect of saving this text/html
is Dreamweaver writing all the binary image files to disk that can be
shared via many pages. If you are using placeholder images to create
the text/html while another person is creating the real images, you
should run into a similar case as our tool chain.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Oct 16 23:11:03 2003