Menu
▾
▴
#26 Two changes+one new directory = fail
We have two developers here who created new files
files within a new directory. Changes 2888 and 2940
each have files that belong to this new directory.
When change 2888 is applied to a tree, hop seems to
check out all the files in the new directory.
Everything is brought down, including the files that
are in change 2940. This causes the build to fail.
Logged In: YES
user_id=161477
Hmm. Is there any way in CVS to check out a new directory
but NOT all the files in it?
Logged In: YES
user_id=280857
I'm not sure on that. When I tried searching for something
along those lines, the best I could find was the -d flag to
check out new empty directories. Didn't find anything
specifically related to checking out subsets of files.
Logged In: YES
user_id=209227
I don't think there is any way to do any CVS commands on
just directories. You can specify "-l" to avoid recursion to
subdirs, that's the closest they seem to get.
Checking out the whole contents of the directory in this
scenario was a hack put in to work around the problem where
Hop used to clobber files in this situation, which is even
worse.
The only solution I can think of is pretty gross:
1. If the directory is already there, move it out of the way
2. Do the cvs update on the new directory
3. remove the files from the new directory
4. copy the contents back from the moved away directory into
the new CVS created directory