-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Denis,
Am Freitag, 28. M�rz 2003 10:20 schrieb Denis JULIEN: > Hi, > I have to implement a cvs for a multiple developers environment. I have > installed it without problems and I've tested the major functionalities and > it seems working fine. It's my first time on this kind of versioning system > and I don't know the good practice in term of sources organization for a > project. For example, I'm asking if we have to create a repository for > each project or create only one repository and under it, create one module > for each project. Maybe somebody can tell me what are the good practices or > where I could found examples or typical and practical implementation of > cvs in multiple developers environment. Thank in advance for your help. at our company (5 workers, Linux), we use 3 Repositories: /home/cvsroot containing normal projects, one module for each project. /home/webroot containing web projects, one module for each project + one module called common also used by other projects /home/sysroot containing a module sysroot for the administration of the machines and the user management. I don't know wether that can be considered best practice, but it works well for us. To restrict rights, for each repository there is a group. To access a repository the person must be group member. Access to CVSROOT is restricted by using the sticky bit. Some modules are restricted furthermore by having a group for them. directory rights for repository and module directories are set to 2770 (rwxrws---). Bye - -- ITCQIS GmbH Christian Wolfgang Hujer Gesch�ftsf�hrender Gesellschafter Telefon: +49 (0)89 27 37 04 37 Telefax: +49 (0)89 27 37 04 39 E-Mail: [EMAIL PROTECTED] WWW: http://www.itcqis.com/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+hClezu6h7O/MKZkRAuVpAJwP0M/raheIKnHP55UMW/g6XWf9mACgle1n rwHJSl7kOB3T92eBPswEuKo= =S6Q2 -----END PGP SIGNATURE----- _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
