Re: CVS Import Inaccuracies - Please Respond

[Bernd Jendrissek]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wed, Aug 10, 2005 at 04:31:10PM +0200, Oproescu Bogdan (KTXA 3) wrote:
>    What is going on here?? Why is CVS checking out the "file_1.txt"
>    and "file_new.txt" files? Or is it because they ARE the HEAD
>    Revisions of these files in the "server_test_module" module, since
>    CVS did not increment the Version Numbers of the remaining files in
>    my structure above for the 2nd to Nth CVS Imports, which did not
>    include "file_1.txt" and "file_new.txt"??

That would be my guess - there is no way, during import, to tell CVS
"this file is NOT present".

>    Here, we either have another CVS Bug, or at least a very inaccurate
>    way to do cvs imports. Note that I can repeat this test using the
>    command "cvs checkout -R HEAD server_test_module" and get the same
>    results as before, so this is not the reason. Worse yet, we cannot
>    even specify exactly which files we want from our "cvs import" with
>    the "-R" flag on checkouts. 

cvs checkout -R HEAD server_test_module
  will checkout HEAD (module name!) server_test_module *R*ecursively.
  In fact, I get this:

cvs server: cannot find module `HEAD' - ignored
cvs [checkout aborted]: cannot expand modules

cvs checkout -r HEAD server_test_module
  will checkout HEAD *r*evision of module server_test_module.

Note difference in case!

When you do import, you specify vendortag, no?  Why don't you checkout
with that?  cvs checkout -r vendortag42 server_test_module

HTH
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQFC+h4o/FmLrNfLpjMRArc8AJwI0GAzC0BGySjumFRG5+Qo3PIgUgCdF5QO
/FjhWNVRBG/zvEnbZawlqlU=
=A4Tz
-----END PGP SIGNATURE-----