William Chops Westfield <billw@CISCO.COM> wrote:
>It SHOULD be possible to put some "modern" wrappers around RCS,

   I have seen a shareware package that does something like this.
   I did not spend any time trying it because I had already worked
   out the command line stuff.

   I usually add something like the following to the bottom of
   the makefile:


    # RCS Utilities:
                                   #These assume a directory 'RCS' just
                                   #under the working directory.


put:                               #Check out the project files from
        ci *.asm                       #archive.
        ci *.inc
        ci -u makefile

get:                               #Check revised files into archive.
        co RCS/*.asm                   #Note: RCS is somewhat case dependent
        co RCS/*.inc                   #and likes '/' not '\'.

nolock:                            #Disable locking.  I'm the only one
        rcs -U RCS/*.*                 #working on these modules.

name:                              #Give a group of revisions a name.
        rcs -n$(name): RCS/*.asm       #A given project release will typically
        rcs -n$(name): RCS/*.inc       #have different revisions among the
        rcs -n$(name): RCS/makefile    #various modules.   e.g.:
                                   #  make name name=Rel_1_3

find:
        co -r$(name) RCS/*.asm         #Get the various revisions corresponding
        co -r$(name) RCS/*.inc         #to a given release.
        co -r$(name) RCS/makefile      #   make find name=Rel_1_3



This may be a little crude but it works for projects typical of the
scope of a PIC project.   It has saved my butt on more than one occasion.


--
Bob Fehrenbach    Wauwatosa, WI     bfehrenb@execpc.com