My solution is to use a script for check in and check out.
The check in script will find the folders that should be opaque and tar
them. This tar file is the submitted.
The check out script is looking for tar files, and untars them. It also
generates a file which contains the revision of the tar file it comes
from, and the exact time it was untared.
The check in script is using this file to determine if the folder is
synchronized with the tar file, so it don't have to tar down unchanged
folders each time you check in.
I have also made a update script that will check if the tar file is
newer than the untared folder, and ask if you want to untar it.
This solution works on a well disciplined team using well known hardware
and software, but it is not very comfortable to maintain. Suddenly,
something goes wrong for no good reason.
Kjell
>
> Is there really a good workaround for this? Other than, say,
> tarring up any bundle files (like, say the Resources folder
> in my project) and checking those in? Is the standard
> technique to use some sort of scripts that do this
> automatically on check-in and check-out? What do Mac
> developers do at this point?
>
> -Mike
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Dec 2 13:25:16 2005