Sender: gryschuk@scf.sk.ca
Message-Id: <35DDD0D7.A6340BAA@scf.sk.ca>
Date: Fri, 21 Aug 1998 13:56:07 -0600
From: Gerald Gryschuk <ggryschuk@scf.sk.ca>
Organization: Saskatoon Cancer Centre
Mime-Version: 1.0
To: Byron Nikolaidis <byronn@insightdist.com>
Cc: "Thomas G. Lockhart" <lockhart@alumni.caltech.edu>,
	Postgres Interfaces Mailing List <pgsql-interfaces@postgresql.org>
Subject: Re: [INTERFACES] iodbc interface on Unix
References: <35D99896.DFB21123@alumni.caltech.edu>
	<35D9D132.4DE6ACB8@insightdist.com> <86iujpr0qh.fsf@avd.gcom.ru>
	<35DAD65D.34165A2F@insightdist.com>
	<35DAE850.93FC000C@alumni.caltech.edu>
	<35DB06BB.16F5D38D@alumni.caltech.edu>
	<35DB1A0A.53F5BD81@insightdist.com> <35DB2F55.CF1072DA@scf.sk.ca>
	<35DB3107.894B0E3C@insightdist.com>
	<35DD97AF.30F23F27@alumni.caltech.edu>
	<35DDA3D3.D39F5846@insightdist.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Byron Nikolaidis wrote:
> 
> Thomas G. Lockhart wrote:
> 
> > 3) Many, but not all, of the source code files have DOS-specific EOL
> > characters. I'd like to strip those out of the code which is sitting on
> > Unix boxes, and have them correct when sitting on your DOS machines too.
> > Can we transfer files using FTP ascii transfers to fix the EOL problems
> > in the future? Or is there another way which will get this fixed up?? In
> > the meantime I will clean up all the files I have, and then can get them
> > to you via the Postgres web site.
> >
> 
> OK.  I do transfer files to Postgresql.org using ftp ascii.  Just the
> postsrc.zip distribution would have dos crap in it.

I noticed this too the first few times I unzipped postsrc.zip until I
remebered that
unzip(I'm assuming Thomas your using the same one I am) has a "-a"
option to convert
all text files to the proper line endings regardless of where the file
originated.
i.e. if you do "unzip -a postsrc.zip" the problems with DOS EOL
characters goes
away.

-- 
Gerald Gryschuk(ggryschuk@scf.sk.ca)
Programmer Analyst
Saskatoon Cancer Centre
((306)655-2746)