Tweet
I've been thinking about how best to relate local installs of CTP2 to svn checkouts. We need some easy way to transfer newly checked out / compiled material to a local install, but I think it would be unwise to have the checkout and local install in the same place.
The solution most obvious to me is to have a script which copies things from the checkout directory to the local copy. Of course, this can be done manually, but it's a nuisance to avoid copying all the .svn directories too. I was thinking of something along the lines of:
I think this would work, but the last bit at least seems a little clumsy.
An alternative is to make use of svn export - but I can see no way of making that work without excessive network access - it seems to make more sense to use the files which are already present.
Does anyone have any other suggestions or ideas?
As an additional advantage, essentially the same script will also allow easy creation of directories to zip up to make playtest versions.
The solution most obvious to me is to have a script which copies things from the checkout directory to the local copy. Of course, this can be done manually, but it's a nuisance to avoid copying all the .svn directories too. I was thinking of something along the lines of:
Code:
cp -u ctp2_code/ctp/ctp.* $LOCAL/ctp2_code/ctp/
cp -u ctp2_code/ctp/dll/map/* $LOCAL/ctp2_code/ctp/dll/map
find ctp2_data -wholename '*.svn*' -prune -o -type f -exec cp -u "{}" "$LOCAL/{}" ";"
An alternative is to make use of svn export - but I can see no way of making that work without excessive network access - it seems to make more sense to use the files which are already present.
Does anyone have any other suggestions or ideas?
As an additional advantage, essentially the same script will also allow easy creation of directories to zip up to make playtest versions.