Highly annoying packaging change from 2.8 -> 2.9

[Martin v. Loewis]

> I noticed this.  But it remains the case that gcc 2.8.1 has a
> top-level INSTALL file and gcc 2.95.2 has a top-level INSTALL
> directory.  (I didn't make up this problem, honest.  cvs import
> barfed, and it barfed for this reason.)  And the top-level INSTALL
> directory in gcc 2.95.2 just has a file named README in it telling
> people to go look somewhere else; there's no reason I can divine why
> it shouldn't have been just a file named INSTALL.

I must be missing something. Why would the command sequence

tar xzvf gcc-2.95.2.tar.gz
cd gcc-2.95.2/gcc
cvs import gcc FSF r2.95.2

fail? cvs import would not even see the top-level INSTALL directory,
as you would be importing a subdirectory, not the entire tree.

If you do import the entire tree, then how can you make use of your
pre-existing CVS tree? Non of the old files would be in place anymore.

So I can easily that this is a problem for you. But I do believe it is
your error, not one in gcc. CVS is well capable of importing
directories, even if they are called INSTALL :-)

Regards,
Martin