I fear the impending switch to subversion will have a negative impact on
the future development of gfortran due the rather limited number of people
who actually supply patches and the sudden increase in hardware
requirements. For example, I find
troutmask:sgk[204] du -sh gcc40 gcc41 trunk 241M gcc40 <-- CVS 4.0
branch 275M gcc41 <-- CVS mainline 694M trunk <-- svn mainline
This is one of the less fortunate aspects of svn. A lot of that
increased space is due to the fact that every single file in the
repository is duplicated. Once in its normal location, and again
in the .svn directory. This "feature" has been much-discussed.
Search the svn archives for "textbase penalty". I am glad I am
not the only one who feels that duplicating every single file is
a problem. If you bring it up on teh svn list though, be prepared
to be regailed with the merrits of being able to sit on an aeroplane
and do an 'svn diff' with no access to the repository (because
we all know that most serious developers spend most of their time
in planes, unattached to their repo network).
I recently tried to re-open the discussion on the svn list but
got nowhere. I would *dearly* love to see an option to svn that
uses a simple checksum or something to figure out if a file has
changed, or an 'svn edit' that copies the file to the textbase
on an as-needed basis. I fear it will never happen though.
I too have to purchase a new hdd to do gcc work on, because my
8G drive just isn't enough any more. On the bright side, I will
be replacing an old SCSI-II hdd with a 140G U320 drive, so svn
can check the files out in triplicate for all I care :)
Kean
