Greetings!
When our build tool recognizes that someone has removed a CVS module from a
build area, I had planned to "cvs release -d $module" to remove it from the
build area and then do a "make clean" everywhere to make sure I had a clean
build area.
I was bummed to find out that 'cvs release' doesn't take a module definition,
but a DIRECTORY. I would think if I could checkout a module, I would be able
to remove a module. Even better, a "-f" option to force the removal even if
there are locally-modified files would make this whole thing much more
automatable.
Does this sound reasonable? Possible? Desirable?
:)hal mahaffey
