FreeTDS Development Group

["James K. Lowden" <jklowden AT freetds.org>]

Craig A. Berry wrote:
> good snapshots would be a big help.   
> Or some other way to generate the bits that need to be generated.   

Ach.  I'm so sorry to have wasted your time, Craig.  

I just uploaded snapshots.  That out to get you going.  

I'm also attaching fwiw the BSD makefile that I use to generate the
snapshots.  If you're so inclined, maybe you can see why the upload fails
to happen.  

Until a few months ago, the nightly snapshot was handled by a simple
script that ran every night, provided the system was up.  Then I had the
bright idea to provide a "nightly" snapshot of the release, too, so that
people would have immediate access to patches.  But it didn't make sense
to generate the release tarball nightly, because patches are applied
irregularly.  I wanted the tarball date to reflect the latest patch, so
that people could gauge whether or not an earlier tarball they had was
still the most recent.  

How to do that?  Comparing MD5s seemed like the right way.  And still
does.  But I seem to have been too clever by half, and can't get the thing
to go forward when it should.  Bah.  

I don't have time tonight to look at it.  I will get to it as soon as I
can.  If someone else spots something, it might speed things up.  

> IMO, autoconf is a pretty severe fate to inflict on anyone who just  
> wants to build from the current development stream.

Absolutely.  

Regards, 

--jkl

Attachment: Makefile.freetds.nightly
Description: Binary data