Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-ID:	<3EA3FF7E.3030202@etr-usa.com>
Date:	Mon, 21 Apr 2003 08:26:06 -0600
From:	Warren Young <warren AT etr-usa DOT com>
User-Agent:	Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language:	en-us, en
MIME-Version:	1.0
To:	Cygwin-L <cygwin AT cygwin DOT com>
Subject:	Re: Is Cygwin really required?
References:	<Xns9361B766BBBBAlucianoavgmxnet AT 80 DOT 91 DOT 224 DOT 249> <b7us4r$bcb$1 AT main DOT gmane DOT org>
In-Reply-To:	<b7us4r$bcb$1@main.gmane.org>

Rolf Campbell wrote:
>>
> The Win32 version will not support posix paths.  But, other than that, 
> it should still work fine.

You may also get some strange line ending translation problems if you 
don't use the one compiled under Cygwin.

If you really must have the brandest newest version of sed, I'd get the 
source and rebuild it yourself.  It shouldn't be difficult.  The main 
trick is then coping with future upgrades; you don't want to have both 
/usr/local/bin/sed and /usr/bin/sed, for example.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -