[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

commit 101

From: jason
Subject: commit 101
Date: 4 Oct 2004 13:40:45 -0700

CVS newbie here trying do a simple test.

I have application files under /a/jcl I want to protect with

I created a repository under /a/cvs using user cvs

cvs -d  /a/cvs init

$ ls -ll /a
total 0
drwxr-xr-x   6 cvs       cvs             96 Oct  4 14:46 cvs/
drwxrwxr-x   3 auser     dev             96 Oct  4 14:54 jcl/

$ ls -ll /a/cvs
total 2
drwxrwxr-x   3 cvs        dev           1024 Oct  4 12:08 CVSROOT
drwxr-xr-x   3 cvs        cvs             96 Oct  1 12:32 src

As the cvs user, I imported /a/jcl source into the repository:

cd /a/jcl
cvs -d /a/cvs/ import jcl jcl_project ver_0-1

got this:
N jcl/jcl1
N jcl/jcl2
No conflicts created by this import

looks good so far I think.

now as userb (my test developer who's in group dev), I am able to
checkout those files and I thought commit them. I can see it committed
them in the repository, but not in the original location..


$ cvs -d /a/cvs/ checkout jcl
$echo change jcl2 >/jcl/jcl2
$cd jcl
$ cvs commit

new revision: 1.5; previous revision: 1.4

So here's my dumb, newbie, highlevel question - when I created the
repository  /a/cvs/ and added a project /a/jcl/ to it I was under the
impression that somehow I'd be able to version the original /a/jcl
source directory with CVS commands. It appears commit is only updating
the repository. I can tell the repository is getting updated with the
commit as checkout shows changes, but /a/jcl is not. How do I verion
/a/jcl, understanding that userb is unable to write to /a/jcl becasue
group dev does not  have Write to that directory (this of course is by
design to enforce the use of CVS). Am I correct in pressuming that CVS
will be able to write files where users can't without using CVS?

In very simple design, If I'm administrating cvs with user csv, and
administrating an  application with user usera,  and have developer
user userb in group dev, and my repository is under /a/cvs and my
protected application sources are under /a/jcl. What's a simple
security scheme (using groups) that keeps cvs admin files under cvs
control, application files (/a/jcl) under usera , but allows userb to
version /a/jcl recorded under cvs.

Many thanks in advance for any help or information.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]