The correct procedure to commit the configure-related files is:
% cvs commit acconfig.h aclocal.m4 configure.in
- % autoconf && autoheader
- % cvs commit config.h.in configure
- % make stamp-h.in
- % cvs commit stamp-h.in
+ % autoheader; autoconf; date > stamp-h.in
+ % cvs commit config.h.in configure stamp-h.in
-If you haven't changed all of those files, just commit the rest in the stated
-order (e.g. cvs commit acconfig.h config.h.in stamp-h.in). The reason for
-the sequence is the RCS Id strings in the edited files -- they change when
-you commit the changes.
+The reason for the three-step commit is that configure.in contains the RCS $Id
+keyword, so when you commit it, a new version is written locally. Therefore,
+the autoconf regeneration should be held off until after the commit, or your
+local stamp-h.in will become out-of-sync with the CVS version (granted, not that
+big a deal). For the second step, you're doing the same commands as a
+`make reset' would do, but using that command would require extra configure runs
+to make Makefile be up-to-date.
-You can run just "make" instead of the other commands in between cvs commits.
+If you haven't changed all the files noted above, just commit the ones you have
+changed, in the stated order (for instance, configure.in, then configure and
+stamp-h.in).
-------------------
MTS code not specific to any single MTS apparently goes here.
zotnet/tws/
- No idea what "tws" stands for, other than 't' almost certainly standing for
- "time". Date and time manipulation routines go here.
+ "tws" apparently stands for "time with structure", a rather odd phrase.
+ This directory used to be the place for date and time manipulation code, but
+ currently nothing in here is compiled. There are new, more portable
+ versions of the key files in h/ and sbr/, and this directory will soon go
+ away completely.
-------------------------------------------------------
projects / mmh / blobdiff