Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
On Wed, 19 Oct 2005 18:15:55 +0100, Tony Hoyle <tony.hoyle at march-hare.com> wrote: >bwhicks at aep.com wrote: >> >> Is this correct? Why? >> >group and passwd are considered security sensitive, so you can't add >them to CVSROOT to avoid people checking them out and getting lists of >active users/administrators (and in the passwd case, possibly their >passwords too). > Does this mean that access to CVSROOT/modules and CVSROOT/modules2 is also restricted (on Windows 2000)??? We have switched to using modules quite heavily and will probably go for modules2 once I can find a recent version of CVSNT that does not carry with it a caveat or two... But my developers need to maintain their modules in the modules file since we have rather complex software with many interrelated files from various physical modules in almost all of them. If they are restricted from checkout/update on these files in "recent" CVSNT versions then I cannot upgrade (again...). Very important issue for me. BTW you did never answer my post on the modules2 handling I posted before. And the cvs.chm file even today (I rebuilt it an hour ago) does have a marker in it for modules2 to the effect that you need to expand on the descriptions... /Bo (Bo Berglund, developer in Sweden)