Xref: utzoo comp.unix.questions:22984 comp.unix.wizards:22494
Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uunet!fltk!dnb
From: dnb@fltk.UUCP (David Buonomo)
Newsgroups: comp.unix.questions,comp.unix.wizards
Subject: Question about RCS check-in
Keywords: RCS, ci, help
Message-ID: <558@fltk.UUCP>
Date: 15 Jun 90 18:45:10 GMT
Distribution: usa
Organization: FileTek, Inc. (fltk), Rockville, MD
Lines: 22

We are using RCS to "control" our source.  Our strategy has been to keep a
read-only copy of each source file checked-out after a check-in (ci -u <file>).
This allows us much faster compile/link phases when we build an entire system
(there are quite a few source files; > 2000).  The system build script simply
runs through our baseline tree running any makefile that it finds which in turn
will recompile/link recently touched source files.

The problem is that the modification time on the source file changes when the
check-in occurs.  This will cause that file to be recompiled (remember make)
even though there was no change to the file, only its modification time
changed.

Has anyone else experienced a problem of this type?  I would appreciate hearing
any approaches to how this was resolved.  I am currently thinking along the
lines of writing a program that will record the current modification time of
the file via fstat, check-in the file via ci, and then restore the modification
time via utime.  Although this will probably work, I feel that there should be
SOMEONE out there that has been this route that may have a more elegant/simpler
solution.

David Buonmomo
uunet!fltk!dnb