FreeTDS Development Group

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

> From: ZIGLIO Frediano [mailto:Frediano.Ziglio AT vodafoneomnitel.it]
> Sent: October 16, 2002 6:20 AM
> 
> > I'm going to remove txt2man from our cvs and change the 
> > doc/Makefile such
> > that it doesn't build man pages unless `which txt2man` 
> > returns a positive
> > result.  That way, he who will build the docs will find out 
> > he needs certain
> > freely available tools, and anyone else won't trip on them.  
> 
> IMHO it's a bad things. txt2man is not installed by default 
> by many system.
> Or you build and distribute only the compiled things or it 
> best to mantain txt2man in CVS.

Here's how I see it, Frediano.  

We didn't write txt2man, so it shouldn't be in our source repository.  I'm
happy to put it on ibiblio, in misc, so there's a convenient place to find
it, but if we're not maintaining it, it doesn't belong in cvs.  

Remember, the only people affected by this are folks using cvs.  Tarballs
include prebuilt documentation.  

"installed by default" doesn't hold water, as my grandfather used to say.
Lots of distributions don't install autoconf; none of them has the bleeding
edge libtool we're talking about using.  If you want to build from cvs, you
have to have your toolchain ready.  If you want to build FreeTDS
documentation from cvs, you have to have txt2man and OpenJade.  What's the
big deal?  If you don't have them installed, you still get libraries.
userguide.sgml and man pages in text form will still be in your source tree,
just not installed.  How bad is that?  

I'm going to stop here before Nick reminds me I'm a lazy turd for not
writing a proper man page in the first place.  

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 for certain accounts we do not accept
orders and/or instructions by e-mail, and for those accounts we will not be
responsible for carrying out such orders and/or instructions. Kindly refrain
from sending orders or instructions by e-mail unless you have confirmed that
we accept such communications for your account. Please also note that to
satisfy regulatory requirements we review the outgoing and incoming e-mail
correspondence of staff members serving certain functions.