I've been running into an issue several times that I'd like some advice
on how to solve.
We have a project where certain files and file structures are
programmatically generated. These structures and files are then checked
back into the repository and are used to build the system from scratch,
they're best described as a bunch of categorized config files. The
problem I'm having is that in order to accurately reflect the changes
that have occurred to the system it seems best to wipe the dump
location's target before initiating the dump. This ensures that we
capture the state of the system without orphaned files and folders of
the previous dump getting in the way. This unfortunately eliminates
certain subfolders and the .svn folders they contained. They are then
replaced by, in most cases, identical subfolders that don't contain the
.svn. When I try and do an add, update, commit etc... it locks the
working copy such that svn cleanup can't fix it until I've removed the
unversioned generated files and folders.
Is there any way to have subversion restore the .svn folder for these
generated folders? Our current workaround is to leave the folder
structure intact and force the developer to remove the folders by hand,
but given the number of files and folders we're dealing with this is a
Bolo Systems, Inc.
(303) 987-2238 x 107
(720) 212-0687 Direct
Received on Thu Feb 1 17:40:05 2007