Highly annoying packaging change from 2.8 -> 2.9
Greg Hudson
ghudson@MIT.EDU
Fri Apr 7 19:39:00 GMT 2000
>> In gcc 2.8.1, there is a file at the top level named INSTALL. In
>> 2.9.2, there is a directory at the top level named INSTALL
>> containing a single file "README".
> Please look again. Everything that used to be top-level, is now in a
> subdirectory named 'gcc', including INSTALL.
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.
> As for CVS: You are certainly free to maintain your own
> tree. However, for the more recent releases, you can get the full
> change history from the CVS at gcc.gnu.org.
You misunderstand; we import gcc into a CVS repository because we have
local changes (just the build system, for our environment), not
because we're interested in the change history.
> P.S. It's 2.95.2 (two-ninety-five-two), not 2.9.2
Yeah, my bad, sorry.
More information about the Gcc-bugs
mailing list