cvs repository control

[Jesse]

eh I post here because im not sure where to post anywhere else

A friend and I have set up a cvs repository and everything works great except for the fact that cvs is absolutely horrible when it comes to security. We've figured out the pserver crap (to be used with ssh tunneling??) and made due with the readers and writers files (for read-only or read-write access to the whole repository) but there are still 2 sticky points:

1) Should ssh tunneling be the way to go using pserver or should we try gserver? Looking for ease of use, speed, and being relatively transparent to our users. Any good documentation of using gserver?
2) How do you let developer_1 work on project_1 and project_3 but not on project_2 in the repository? Do any easy solutions to this exist that do not require adding several new accounts to the system and extra groups to fudge around this fundamental issue? Can you point us in the direction of relevant documentation?

I've already been using www.cvshome.org and the CVS book to help but they are still lacking in this advanced configuration. The best they give are examples of literally only allowing one developer to work on 1 project at a time or just giving them read-write access to the entire repository ...

[klieber]

Moving this to general linux since it isn't specific to Gentoo.

Might consider searching google

--kurt
_________________
The problem with political jokes is that they get elected