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 firstname.lastname@example.org.
Create a separate repository for each customer. If you like, combine it with DNS so that the CVSROOT for cust1 is e.g. :pserver:cvs-cust1.yourdomain:/cvs/cust1 (This is the setup we use were I work). -Torsten Adam Shand wrote: > Hi. > > I have a small problem that I'm hoping there is an easy solution to. > I'm setting up a CVS server that our engineers use to collaborate on > code with our customers. If possible I'd like to do all access > control with file permissions rather then repositories. > > I've setup a directory structure like this: > > c:\repositories > \temp > \lock > \cvsroot > \CVSROOT > \cust1 > \cust2 > > It's important that cust1 NOT know that cust2 exists on the server > (and vice versa). The way I attempted to do this was to create a > group per customer and give full permissions on their module > directories and on all the directories about that give *only* traverse > permissions.