bcs_soi \- the Baseline Configuration System (BCS) for SOI.SH SYNOPSIS
BCS is a set of utilities for maintaining a single baseline and multiple
staging areas for a software development effort. BCS provides some configuration management functionality as well as the means for multiple users to work concurrently on a common source tree with minimal conflict.
The baseline directory is /home/soi/CM which is owned by CM.
When you follow the directions in DETAILED DISCUSSION below you will have your
own staging area that "looks into" the baseline. .SH SUMMARY OF USE
.IP "\fBsync_staging [-r] directory\fR" 5
Syncronize a staging directory with the baseline.
.IP "\fBbcsco file\fR" 5
Check out and lock a file. You can now edit the file.
.IP "\fBregister_file file\fR" 5
Register a new file with BCS. This makes a new file known to BCS and checks it
out and locks it for you.
.IP "\fBrcsfix file\fR" 5
Adds the rcs id strings to the file. Detects which type of file it is and adds
the appropriate strings. For a .c file make sure that you edit below the char rcsid string.
.IP "\fBbcsci file\fR" 5
Check in and unlock a file. A read-only copy is left in your directory. This
updates the file in the RCS directory in the baseline corresponding to the staging directory that the command is done from. Other users do not see the updated file but will get it if they check it out. .IP "\fBupdate_baseline file\fR" 5
Updates the file in the baseline directory corresponding to the staging
directory that the command is done from. This allows all users to now see the file.
.IP "\fBstage file\fR" 5
Removes the link of the file into the baseline and copies the actual file into
your directory. The file is still read-only. If you want to edit it you must check it out.
.IP "\fBunstage file\fR" 5
Replaces the file with a link into the baseline. This is normally used when you
have your own copy of a file but want to restore it the the copy in the baseline, for example, abandon your own copy of an executable.
You will be warned if you have checked out the file. If you override the
warning you will get the link to the baseline version of the file, but the file will still be locked by you.
.IP "\fBbcs_info file\fR" 5
Provides various information about what BCS detects as the state of the file.
.IP "\fBlsbcsco directory\fR" 5
This is a perl script in /usr/local/scripts. It lists the files in the
directory that have potentially been checked out with the bcsco command. You could also do something like list all your plain files that are not .o files: "find . -type f ! -name `*.o' -print". (Obsolete: use lslocked) .IP "\fBlslocked directory\fR" 5
This is a perl script in /usr/local/scripts. It list all the rcs checked out
files (i.e. locked) in the given directory. The default is ".".
.SH DETAILED DISCUSSION * Each user must be a member of the group "SOI".
* Each user must do a "mkdir STAGING" in their home directory or some appropriate place. The full path name of this directory that you have just made (for example, /home/you/STAGING) is refered to as staging_directory below.
* Call "/home/jim/STAGING/stage_setup staging_directory". You MUST specify the full path name of the staging_directory. This will create a .bcsinit and a .baseline_path file in the staging_directory.
* At the end of your .login or .cshrc source the .bcsinit file in the staging_ directory. This should be done at the end of your file because it should override variables that you may already have set, such as $MKROOT.
* In you path, define staging_directory/bin/_$MACHINE. Make sure that you remove any /home/soi/new/bin/_$MACHINE from your path.
* cd to your staging_directory and do "sync_staging -r ." This will syncronize your staging area with the baseline. The CM will notify everyone if it becomes necessary to ever do this again. In any event you may do this at any time with no harm.
* NOTICE! On fault make sure that your rcs is the /usr/local/bin one. The /usr/sbin/rcs does not pass the BCS regression tests.
USING THE STAGING AREA:
After you have done the above your staging area is ready for use.
You only work in your staging area. No one cd's to any /home/soi/CM
directory. The baseline belongs to the Configuration Manager.
Your staging area will initially have links to everything of importance in the baseline. When you want to edit something you must first check it out from the baseline by saying:
bcsco is an alias for the correct bcs version of the rcs checkout command with a standardized lock flag. You never use the rcs commands directly.
If someone else has already checked it out, you will not be able to get it. You will be told who has already checked it out. If you do not check it out you will not be able to edit it as it will be read only.
You edit the file as you want and do a make on your taget. The objects and the new executable are local in your staging area. No one else will see them. When you're happy that it's all ok, you check back in your file with:
This removes your lock on the file and makes it read only again.
A local copy is retained so that you do not have to check it out again to view
the file. This updates the RCS log of your file so that the next person checking it out will see your changes. The .c file in the baseline is not updated until you do an update_baseline. Only the CM will see this .c file.
It's not really necessary for you to update the baseline as the CM will get
all of the latest stuff from the RCS directories before they make. In practice it might be a good idea to let the CM see the latest stuff without having to do anything explicit. However as we learn as we go, we may decide elsewise. So for now let's say that you do an update_baseline.
You update the baseline by saying:
You can wait to check in and update the baseline until you have completed a set of files that are related. Cooperation is required in that you don't check out a popular file and then sit on it.
If you are creating a new file, first do:
This will create a the file in the baseline if it doesn't already exist and lock it for you. Then put in the rcs ident information by:
Now edit you file normally, and make sure that for a .c file you start you edit just below the first line that has the char rcsid definition.
When you have completed the file do the bcsci and update_baseline. You may do
a register_file if the file already exits in your staging area, however it is good practice to do the register_file first in order to reserve that file name amongst all the users. The CM must initially set up any new directories.
If you have checked out a file and later decide that you don't want to change anything, but want to remove your lock on it, just do another bcsco and answer yes on the overwrite warning, and then check it back in.
Notice that when you update the baseline with a new .c file you have not changed the baseline executables. This can only be done by the CM.
When everyone has agreed that they have submitted everything for the next
SOI version, then the CM does the master build in the baseline. Optionally the
CM may also be requested to make a new library for example, that people may
need to do their new version development. If the new library is a flop, the CM has a way of remaking the previous one.
* The man pages are under RCS but do not have a $Log ident, as this will be displayed on the man page.
* The lib make files have been modified to make locally and do a mv to the target. This is as done in other make files and is needed for our BCS implementation.
* Keep an eye out for any expilict reference to /home/soi/new that was used instead of MKROOT.
* Forward all pathology reports to CM.
.SH SEE ALSO
BCS: A Baseline Configuration System Version 2.0 beta Jan 10, 94
RCS - A System for Version Control Jan 3, 91
1994-03-03 SOI Version 0.9
.#$Id: bcs_soi.1,v 1.4 1994/05/27 22:40:35 jim Exp $ .#$Source: /home/soi/CM/man/man1/RCS/bcs_soi.1,v $ .#$Author: jim $