> On Fri, Sep 14, 2001 at 12:31:44AM +0530, P.V.Sridhar Reddy wrote:
>> My problems are:
>> 1) How do i create the repositories???
> cvs import a file to start with (say, a readme explaining what the project
> is). Or do something like "cvs co -l . ; mkdir foo ; cvs add foo"
Often it is useful to first create an empty repository as
cvs -d /the/cvs/root/directory init
this will populate the $CVSROOT/CVSROOT/* files as well.
>> 2) I dont want the developers of one project to be able to do any kind of
>
>> CVS operations on other project.
>>
>> 3) Within in a project, i want only one person to be able to checkin, and
>> for others only checkout permissions.
> Both of these can be handled with usual unix permissions. Use g+rs on the
> top level directory, for instance.
why g+s ? g+rx would seem more logical (g+s sets directory-groupid on file
creation, but files won't be created).
If you have a big directory tree, do
chmod -R go+r,go-w $CVSROOT
find $CVSROOT -type d -exec chmod go+rx,go-w {} \;
Philip
--
Real programs don't eat cache (Malay)
-----------------------------------------------------------------------------
Philip Lijnzaad, [EMAIL PROTECTED] \ European Bioinformatics Institute,rm A2-08
+44 (0)1223 49 4639 / Wellcome Trust Genome Campus, Hinxton
+44 (0)1223 49 4468 (fax) \ Cambridgeshire CB10 1SD, GREAT BRITAIN
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
