Re: [ng-spice-devel] CVS works


To ng-spice-devel@ieee.ing.uniroma1.it
From Paolo Nenzi <pnenzi@ieee.ing.uniroma1.it>
Date Wed, 13 Sep 2000 20:39:04 +0200 (CEST)
Delivered-To mailing list ng-spice-devel@ieee.ing.uniroma1.it
In-Reply-To <39BFC031.72F6F508@analog.com >
Mailing-List contact ng-spice-devel-help@ieee.ing.uniroma1.it; run by ezmlm
Reply-To ng-spice-devel@ieee.ing.uniroma1.it



On Wed, 13 Sep 2000, Alan Gillespie wrote:

> Do you think that I can trust that the fact that the tar
> file seemed to be expanded ok, means that quota
> didn't truncate the file ? Otherwise, since the tar.gz
> was deleted, I didn't get a second chance, so I'll be
> missing some files at the end of the tar file.

Definitively yes! Makefile compiles every file, and configure touches
every Makefile so there is no chance that a file can escape this check. If
a file is lost someway, "make" will ends telling you that a file is
missing. 

> 
> Would tar have detected a premature end of the tar
> file when I extracted it on my laptop ? Is that another
> sign that everything's ok ?

Yes. 


> Otherwise, presumably I can copy all the .c and .h files
> from the previous snapshot (apart from outitf.c) over the
> new snapshot, and that should replace any missing files.
> (I don't want Paolo distracted any more by having to
> remake the snapshot)

If you browse the CVS and look for dotcard.c and outitf.c, click on the
most recent revision number, you will get the source of the file. A simple
cut and paste into an editor, will be sufficient. If you want to learn
cvs, look at /usr/share/doc/cvsbook and download the ps.

> I'll try to find an example that wouldn't be giving away company
> secrets. 

Oops, I thought you were working on publicy available files.

Paolo


Partial thread listing: