This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Using up double diskspace for working copies (Was Re: Detailsfor svn test repository)
Richard Earnshaw wrote:
Why do you need to keep the source around at all (unless you are
actively working on that version)? All you need is the single revision
number string and you can guarantee to get exactly that source code back
at any time you want, should you need it.
Only while the server is up and running, in a sane state, and the
internet connection
to the server machine works all the way from here to there. Which is
not all
the time, I am afraid to say. Someone would also have to hack gdb to
retrieve
the source code via cvs/svn.
Moreover, I often want just a quick look at the source, and a checkout
has quite
a long latency for that.
And finally, sometimes bugs in the checkout process or changes in the
modules file
can cause strange build failures.
If I don't keep around the sources axactly they were checked out, there
is no guarantee
that the build (or non-build) can be reproduced, and if it isn't
reproducible because of
a transient problem, the best way to start is to compare the sources of
the original
checkout with the new checkout... oops, you were just talking of not
having these.
So you should only need at most one copy of the source in your
regression testing system, and when you copy the binaries, just record
which revision they were built from.
Huh? Why would I want to copy the binaries?