Skip to Content.
Sympa Menu

freetds - RE: Corrupt file 0.60rc1

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Lowden, James K" <LowdenJK AT bernstein.com>
  • To: "'TDS Development Group'" <freetds AT franklin.metalab.unc.edu>
  • Subject: RE: Corrupt file 0.60rc1
  • Date: Tue, 10 Sep 2002 12:13:14 -0400


> From: ZIGLIO Frediano [mailto:Frediano.Ziglio AT vodafoneomnitel.it]
> Sent: September 10, 2002 11:58 AM
> >
> > Does rc3 work for you?
> >
>
> It work (it compile) but contain some unneeded file (like CVS one)
> Should these file go to distribution:

no - autogen.sh
no - INSTALL.CVS
yes - doc/CodingStyle
no - doc/developer
no - doc/README.releasing

> No, rpm must find a .spec file inside tarball. It work in such way
> - rpm extract spec from dist
> - rpm build extracted spec

Ah, so why isn't the spec file in CVS?

+++

I'm about to post rc4, trying to combine your ideas and Brian's. Basically,
rc3 was a tarball of the whole CVS tree. I downloaded it here, did "make
dist" (using gnu make), and added the README.0.60. It needs a note about
tds8.

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






Archive powered by MHonArc 2.6.24.

Top of Page