FreeTDS Development Group

["Lowden, James K" <LowdenJK AT bernstein.com>]

> From: Frediano Ziglio [mailto:freddyz77 AT tin.it]
> Sent: February 21, 2003 2:14 AM
> Il ven, 2003-02-21 alle 00:25, Lowden, James K ha scritto:
> > Index: configure.in
> > ===================================================================
> > RCS file: /cvsroot/freetds/freetds/configure.in,v
> > retrieving revision 1.85
> > diff -u -u -r1.85 configure.in
> > --- configure.in        20 Feb 2003 02:46:10 -0000      1.85
> > +++ configure.in        20 Feb 2003 23:21:09 -0000
> > @@ -12,7 +12,8 @@
> >  dnl ------------------------------------------------------------
> >  AC_INIT(src/dblib/dblib.c)
> >  AC_PREREQ(2.53)
> > -AM_INIT_AUTOMAKE(freetds, 0.61)
> > +define(TDSDATE, esyscmd(echo -n esyscmd(date +"%Y%m%d")))
> > +AM_INIT_AUTOMAKE(freetds, 0.62.dev.TDSDATE)
> >  AM_CONFIG_HEADER(include/config.h)
> >  AC_PREFIX_DEFAULT(/usr/local)
> > 
> Same results with
> 
> AM_INIT_AUTOMAKE(freetds, 0.62.dev.`date +%Y%m%d`)

Not for me.  :(  When I run that through m4, I get:

AM_INIT_AUTOMAKE(freetds, 0.62.dev.date +%Y%m%d`)

which later breaks.  Rather than entangle sh and m4 syntaxes, I think it's
cleaner to explicitly invoke the shell with esyscmd.  Here's a simpler
version:

        define(TDSDATE, esyscmd(echo -n $(date +"%Y%m%d")))

> However next day you have to rerun autogen to rebuild configure with
> current date.

Right.  The nightly snapshot script starts with "rm -rf freetds; cvs
checkout...."  It then proceeds to regenerate the configure script.  This
way, the "version" of FreeTDS will include the snapshot date.  One
consequence is that snapshot users will wind up with a different directory
name every time they untar the snapshot.  Some people will like that and
some won't, I guess.  

I added version information at the top of the FreeTDS dump file, ending one
source of ambguity and questions.  

> rpm -Fvh freetds-0.62.dev.20030221-1.i386.rpm !!!

Yup.  

--jkl


The information contained in this transmission may contain privileged and
confidential information and is intended only for the use of the person(s)
named above.  If you are not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient, any
review, dissemination, distribution or duplication of this communication is
strictly prohibited. If you are not the intended recipient, please contact
the sender immediately by reply e-mail and destroy all copies of the
original message. Please note that we do not accept account orders and/or
instructions by e-mail, and therefore will not be responsible for carrying
out such orders and/or instructions.