Re: CVS bug? "cvs checkout: move away bar; it is in the way"

[kynn]

   X-Original-To: kynn@panix.com
   Date: Sat, 5 Jun 2004 19:43:02 -0400 (EDT)
   Cc: bug-cvs@gnu.org
   From: lawrence.jones@ugsplm.com (Larry Jones)

   kynn@panix.com writes:
   > 
   >   % rm -rf Foo && mkdir Foo && cd Foo
   >   % echo -n 0 > bar 
   >   % cvs -d $TESTCVSROOT import -m '' Foo vendor_1 v1
   >   N Foo/bar
   > 
   >   No conflicts created by this import
   > 
   >   % cvs -d $TESTCVSROOT checkout -d . -r vendor_1 Foo

   This is the root of your problems: you're doing a checkout into an
   existing directory that already contains files.  You should always let
   checkout create a brand new directory.

Come to think about it, that explanation doesn't make sense.  After
all, in many situations cvs checkout behaves very similarly to cvs
update, reporting on how the files in the working copy compare to the
ones being checked out.  This behavior simply makes no sense if, as
you say, checkout is supposed to always create brand new working
directories.  In fact, if this were the case, cvs checkout should fail
with a message such as "directory already exists" or "directory not
empty" whenever someone attempted to checkout files into an existing
directory that already contains files.

In light of this argument, I think that what I reported is indeed a
bug.

kynn