:    I have several people who are working on one programming project.  
: The each need to make changes to several parts of the source code,
: sometimes it might be the same file and sometimes not.  I have looked
: at SCCS & RCS, but I don't think they will do what I want.  Here's the
: setup I am looking at...

:     All Source code is here:  /home/<source>
:     Programmer1 working directory: /home/prog1/<source>
:     Programmer2 working directory: /home/prog2/<source>

:   I would like each programmer to be able to "check-out" a copy of
: whatever file they need to work on, while at the same time locking
: out others from checking it out to make any changes.  Once the
: programmer is finished making changes, they will check it in and thus
: other programmers may check them out.  Also, did I mention I would
: like each programmer to be able to keep read-only copies in their
: working directory so they can compile.  
:  
:   The True Source code directory is where the releasable version of
: the code will reside.  Any suggestions?  Am I going about it the wrong
: way?  I am open to an ideas from those who have been managing code
: development.  

We do this with both RCS and SCCS with no problem.
Eg with SCCS
 cd /home/prog1/<source>
 get /home/<source>   #get read only copy of everthing
 get -e /home/<source>/s.file #get editable copy
 make changes/compile changed version
 delta /home/<source>/s.file #update s file
 cd /home/<source>
 get s.file   #update master copy

With RCS it is similar and in some ways easier. One thing that is worth
doing is using RCS subdirs and seting links between them.

     All Source code is here:  /home/<source>
     RCS files for source here: /home/<source>/RCS
     Programmer1 working directory: /home/prog1/<source>
     Contains link /home/prog1/<source>/RCS -> /home/<source>/RCS

 cd /home/prog1/<source>
 co RCS/*   #get read only copy of everthing
 co -l file #get editable copy (automatically follows RCS link)
 make changes/compile changed version
 ci file  #update v file
 cd /home/<source>
 co file   #update master copy

--

Philips Semiconductors Ltd
Southampton                                 My views are my own.
United Kingdom

   I have several people who are working on one programming project.  
The each need to make changes to several parts of the source code,
sometimes it might be the same file and sometimes not.  I have looked
at SCCS & RCS, but I don't think they will do what I want.  Here's the
setup I am looking at...

    All Source code is here:  /home/<source>
    Programmer1 working directory: /home/prog1/<source>
    Programmer2 working directory: /home/prog2/<source>

  I would like each programmer to be able to "check-out" a copy of
whatever file they need to work on, while at the same time locking
out others from checking it out to make any changes.  Once the
programmer is finished making changes, they will check it in and thus
other programmers may check them out.  Also, did I mention I would
like each programmer to be able to keep read-only copies in their
working directory so they can compile.  

  The True Source code directory is where the releasable version of
the code will reside.  Any suggestions?  Am I going about it the wrong
way?  I am open to an ideas from those who have been managing code
development.  

Please post follow-ups to comp.software.config-mgmt or e-mail me
directly.

TIA!
-Walt

[snip]
: :  Also, did I mention I would
: : like each programmer to be able to keep read-only copies in their
: : working directory so they can compile.  
: :  

[snip] sccs desc

: With RCS it is similar and in some ways easier. One thing that is worth
: doing is using RCS subdirs and seting links between them.

:      All Source code is here:  /home/<source>
:      RCS files for source here: /home/<source>/RCS
:      Programmer1 working directory: /home/prog1/<source>
:      Contains link /home/prog1/<source>/RCS -> /home/<source>/RCS

:  cd /home/prog1/<source>
:  co RCS/*   #get read only copy of everthing
:  co -l file #get editable copy (automatically follows RCS link)
:  make changes/compile changed version
:  ci file  #update v file

Correction:
ci -u file  # to keep a copy in the local dir to be able to compile locally.
                    # as specified above in the posters org requirements.

:  cd /home/<source>
:  co file   #update master copy

: --

: Philips Semiconductors Ltd
: Southampton                                 My views are my own.
: United Kingdom

Jeff
[][][][][][][][][][][][][][][][][][][][][][]                    /
[ Jeffrey W. Faist  SSU Team Build Meister ]     \             / /
[ Timberline Tape Division, StorageTek     ]      \\\' ,      / //

[ Audible:  (303) 673-2283                 ]        \_-//' /  //<,
[ Physical: StorageTek                     ]          \ ///  <//`
[           2270 S. 88th St, M.S. 0224,    ]           /  >>  \\\`__/_
[           Louisville, CO 80028-0224      ]          /,)-^>> _\` \\\
[ FAX :     (303)-673-7694                 ]          (/   \\ //\\
[ PGR :     (303)-540-2112                 ]              // _//\\\\
[][][][][][][][][][][][][][][][][][][][][][]            ((` ((
[ The opinions expressed here are my own   ]
[ and not necessarily those of my employer ]
[][][][][][][][][][][][][][][][][][][][][][]

--

        Excellent AIX debugging tools - http://www.tkg.com/

   Gary