FreeTDS Development Group

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

> From: ZIGLIO Frediano [mailto:Frediano.Ziglio AT vodafoneomnitel.it]
> Sent: October 28, 2002 7:59 AM
> 
> 2) snapshot build
> I think we should update our snapshot build process. Now the 
> only build is CVS snapshot. I'd like to add
> - documentation snapshot (so test users can try using update 
> documentation removing the need of docbook)

I don't understand.  The documentation is provided as sgml and html in the
nightly snapshot.  You can't "remove the need for docbook" if the UG is
maintained in docbook.  

> - rpm snapshot (built every day)

In principle, OK.  In practice, the nightly snapshot is built on a NetBSD
machine.  I don't know  if the tools for building a (source?) rpm are
available on that platform.  

What we could perhaps do is let you build the nightly rpm, and enable you to
to scp the file to my build box, which would then upload it.  But I will
look for rpm tools first.  

> 3) distribution
> Why do not use a date instead of a version for releasing 
> snapshot. So we can
> release snapshot always with updated version

Interesting idea.  You mean, for the purposes of the nightly build, change:

        AM_INIT_AUTOMAKE(freetds, 0.60)

to something like:

        AM_INIT_AUTOMAKE(freetds, 0.60-20021031)

Can do.  

> 4) new compile options
> Personally I hate debug code in release so I'd add a 
> --minimun-debug-level
> for disabling some debug/log code generation.

I think this would be counterproductive.  Oftentimes we say to someone
experiencing a problem, "get the nightly snapshot and show us a backtrace".
The more debugging information, the better.  What do you want that strip(1)
doesn't do for you?  

> Other option is to disable the read of environment variable 
> for connecting
> configuration (like TDSHOST, TDSVER), it seem a bit unsecure...

Hmm.  Many applications rely on environment variables.  It seems to me if
you can't control them, you've got more troubles than connecting to the
wrong host.  

Regards, 

--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.