Highly annoying packaging change from 2.8 -> 2.9

[Greg Hudson]

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

> fail?

It wouldn't, but I'm importing 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.

In fact, all the files moved, but that's not catastrophic.  From the
point of view of our source management, gcc 2.8.1 had one structure
and gcc 2.95.2 had another, and the few local changes we had needed to
be propagated from one file to another.  This sort of thing has
happened with other packages we build as well; the solution is not, in
general, to start importing subdirs of the tarfile.