Why not simply define a regular module (instead of an alias module):
hal hal
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 04, 2000 10:31 PM
To: [EMAIL PROTECTED]
Subject: "cvs checkout -c" again
Greetings!
I need WinCVS and "cvs checkout -c" to be able to list all of the modules in
our repository. The problem is, they both only list the contents of the
"CVSROOT/modules" file. (I assume WinCVS uses "co -c")
So, you say, simply add the modules to CVSROOT/modules!
One little problem. If I have a directory in my top level called, for
instance, "hal", and I make the following entry in CVSROOT/modules:
hal -a hal
I get the following message on "cvs checkout hal":
cvs server: module 'hal' in modules file contains infinite loop
cvs server: module 'hal' in modules file contains infinite loop
I need the module definition in the modules file to be the same as the
directory name at the top of the tree. I can't do this for example:
_hal -a hal
To be honest, I think this is yet another reason why "cvs checkout -c"
should
return the directory names at the top of the tree as well as the contents of
CVSROOT/modules.
Or is there some other trick I can use?
Thanks for listening!
:)hal
