Re: snapshots stuck

Craig A. Berry wrote:
> On md5 and snapshots and James's snapshot script, it looks like the  
> script calculates the md5 on a directory:
> 
> 	/usr/bin/md5 $(WORKDIR) > $@
> 
> When I try that, I get:
> 
> % md5 freetds
> md5: freetds: Is a directory
> 
> So where I live, you can't do the md5 of a directory.  Where James  
> lives, you can, but what does it mean?  One of the things it might  
> mean is that on James's system the md5 is doing its magic on the  
> directory file itself, not the contents of the directory.  

Bingo!  

$ mkdir d
$ md5 d
MD5 (d) = 45dceb078703c7df15a46c65ee86f702
$ touch d/t
$ md5 d
MD5 (d) = 945ddd2c59b0fdb0421df0fe823ba177
$ ls > d/t
$ md5 d
MD5 (d) = 945ddd2c59b0fdb0421df0fe823ba177

Craig, thanks a heap!  You can add this to your list of contributions to
the FreeTDS project.  All this time I've been wondering what was wrong. 
The *assumption* that MD5 worked on the tree, I never questioned.  Argh!  

The way home is now short.  I think "find freetds -ls" | md5 will work
fine.  Or, for that matter, "md5 freetds/ChangeLog".  

> comparing md5's of tarballs would be a safer bet.

Generating the tarball doesn't quite work, unless done twice, because the
tarball has a version number derived from the date.  

> Does CVS not have a change number, or a changeset or commit ID that  
> could be compare with a previous one?

No.  Subversion uses a repository-wide version number, though, and
Frediano and I both want to switch.  That's a future possibility: instead
of ".dev.{date}" the development version could be ".svn.{revision}".  

> I don't actually see how make dist could work anywhere  
> unless cp means something rather different on Linux than in BSDish  
> places.  

You might not be aware the distribution tarballs are generated on a NetBSD
system.  

Thanks also for the patch.  Might as well ship the gifs, too.  

Regards, 

--jkl