>>>> "jam" == John A Martin
>>>> "Martin" == Martin Buchholz
>>>> "Re: 21.0 vs 21.2"
>>>> Fri, 1 Jan 1999 19:10:17 -0800 (PST)
jam> Perhaps I need a little remedial CVS tutorial.
jam> 1. Before doing that I can look see how big the tarball is and choose
jam> accordingly where to put it.
jam> 2. When it arrives I can check the signature to tell me the file is
jam> uncorrupted since someone I might know signed it.
jam> 3. Before unpacking it I can see what is there and where it will go.
jam> 4. I can choose to put it where it won't clobber something that I
jam> already have and that works (or least that I know something about).
jam> 5. If I run out of space unpacking it I can without too much trouble
jam> try again someplace else.
If you ALMOST run out of space getting it from CVS, and then do a
build, you will run out of space later during the build of the elc and
info files. Disk management is inherently non-automatable.
Martin> I recommend CVS, though.
Martin> cvs -z9 -d :pserver:xemacs＠cvs.xemacs.org:/usr/CVSroot
Martin> checkout -R r21.2.8 xemacs
jam> At minimum, how can I tell what I'm getting in for. How can I tell
jam> how big it is and where will it land. How can I specify where it will
There doesn't seem to be a way to recursively estimate disk sizes of
an exported CVS directory. A rule of thumb is that a CVS tree is only
slightly larger than the equivalent exploded tarball from the ftp site
without the CVS subdirectories. The really big disk overhead is at
the server, as it should be.
jam> Where should I go to learn how to do these things?