CVS conflict avoidance

[H.J. Lu]

> 
> I wonder if it was possible to hack the CVS repository setup at cygnus
> such that *CVS* would regenerate `*-parse.c' (or similar) whenever
> somebody commits in a change to any of the relevant source files.  Sort of
> like how the files in CVSROOT are kept current.
> 
> I can see two potential flaws in this scheme: nothing guarantees that the
> generated file compiles correctly, and the corresponding file in my source
> tree would not reflect the version in the repository unless I would do
> `update' immediately after the commit.  Perhaps these two can be worked
> around?
> 

I have been using CVS to control my binutils for Linux.
I periodically import the gas snapshot into my CVS. But
I purposely leave out those generated .c/.h files as
well as *.info* from my CVS. One reason for me to do it
is what has been mentioned here. When I make my binutils
snapshots, I generate those files by hand. I wish Makefiles
in binutils can do that for me:

1. Add "make update-generated-files" which works
with both "make update-generated-files" and
"make update-generated-files -f Makefile.in".
2. "make gas.tar.gz -f Makefile.in" will do a
"make update-generated-files" before making the
tar ball.

The same thing can be said for egcs.


H.J.