we probably have an a bit uncommon or even strange directory structure
in our project.
First, there's the main repository storing our source code and some
program resource files. On the other hand, we have a second repository
containing larger binary data files. The binary stuff is in a seperate
repository because of backup reasons and such things.
Now what we do is check out the second (data) repository into a
sub-folder of the first repository's working copy. Ok, the check-out
doesn't work directly, we checked it out somewhere else and moved the
second working copy to its destination. The sub-folder the second
working copy is in is unversioned, so it's not part of the first
repository. Looks like:
OurProject <- Wc of repository 1
\-- Stuff <- versioned folder
\-- Binaries <- Wc of repository 2, unversioned in
\-- More stuff <- another versioned folder
For those who may wonder: it works. No problems caused by adding,
updating or commiting files in the first or second repository.
The only problem we have is that TortoiseSVN doesn't treat the folder of
the second repository (named 'Binaries' here) as a working copy. The
folder is shown without overlay symbol and the context-menu of the
folder doesn't offer the SVN commit/ update commands, only check-out.
However, if one right-clicks in Explorer's list-view on an item withing
the working copy and then immediately right-clicks again on an empty
space, the context-menu for the folder (sometimes) comes up right _with_
commit/ update menu items. And yes, commit/ update then works perfectly
for the whole working copy.
Can this be fixed, so the SVN context-menu will show up correctly for
folder 'Binaries'? Or is this repository structure just too stupid? ;-)
Received on Sat Mar 12 17:46:03 2005