Is there a way that the cvsmonitor can automatically pick up all the modules in the repository for monitoring ?. Do I have to go and add all the modules which i want to monitor manually in the cvsmonitor ?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have never found or read about a way to have it pick up all the modules in a repository, but I'm sure Adam will come along and give the definitive word. There might be a way to add modules from the command line, but I don't know it. There is a command line way to execute cvsexec.pl with the 'updateall' flag. If you go hunting around in cvsexec.pl you might find something helpful that would let you use a list of modules to drive a script.
Cheers,
Doug
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Unfortunately, CVS doesn't advertise the repository structure in any way that I know of.
There is one method of doing it which involves getting the contents of the CVSROOT/modules file, and doing something with that... BUT since CVS Monitor can't do composite modules ( yet ), which is usually what the modules file is used for, it doesn't help us much...
I'm afraid it's as much a limitation of CVS as it is CVS Monitor. I'm hoping one day when subversion get's somewhere closer to a full release, we can add a subversion backend and just be done with it...
But until then CVS still counts a "module" as any arbitrary directory within the repository.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Is there a way that the cvsmonitor can automatically pick up all the modules in the repository for monitoring ?. Do I have to go and add all the modules which i want to monitor manually in the cvsmonitor ?
I have never found or read about a way to have it pick up all the modules in a repository, but I'm sure Adam will come along and give the definitive word. There might be a way to add modules from the command line, but I don't know it. There is a command line way to execute cvsexec.pl with the 'updateall' flag. If you go hunting around in cvsexec.pl you might find something helpful that would let you use a list of modules to drive a script.
Cheers,
Doug
Unfortunately, CVS doesn't advertise the repository structure in any way that I know of.
There is one method of doing it which involves getting the contents of the CVSROOT/modules file, and doing something with that... BUT since CVS Monitor can't do composite modules ( yet ), which is usually what the modules file is used for, it doesn't help us much...
I'm afraid it's as much a limitation of CVS as it is CVS Monitor. I'm hoping one day when subversion get's somewhere closer to a full release, we can add a subversion backend and just be done with it...
But until then CVS still counts a "module" as any arbitrary directory within the repository.