From 2ef1a2bc54aa523b9edbb830959f17a3ed05d74d Mon Sep 17 00:00:00 2001 From: Dan Harkless Date: Tue, 18 Jul 2000 02:07:51 +0000 Subject: [PATCH] I don't understand why Kim's split-up of the autoconf-file cvs commits should be necessary, so I left a little note hoping for someone to explain technically why that should be the case. I certainly never ran into any problems with my old single-commit version (which I added back in along with an explanation of why it supposedly won't always work). Also Kim's text implied that the _only_ reason for the given order is the RCS Ids -- not true -- the timestamps are the main reason a particular order is necessary. Made a couple of other clarifications as well. --- docs/README.developers | 17 ++++++++++------- 1 file changed, 10 insertions(+), 7 deletions(-) diff --git a/docs/README.developers b/docs/README.developers index b243b5d..f93c70b 100644 --- a/docs/README.developers +++ b/docs/README.developers @@ -44,17 +44,20 @@ around with `touch'. The correct procedure to commit the configure-related files is: % cvs commit acconfig.h aclocal.m4 configure.in - % autoconf && autoheader + % autoconf && autoheader # or simply "make" % cvs commit config.h.in configure - % make stamp-h.in + % make stamp-h.in # or simply "make" % cvs commit 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 that the commits need to be split up is that the RCS Id strings +in the files change when you commit, which can apparently mess up the +dependencies. [How? -- Dan Harkless ] If this were +not the case, you could commit with a single make followed by a +cvs commit acconfig.h aclocal.m4 config.h.in configure.in configure stamp-h.in. -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, +in the stated order (for instance, configure.in, then configure, then +stamp-h.in). ------------------- -- 1.7.10.4