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: <01b401c28cc7$934d6a60$78d96f83@pomello>
From: "Max Bowsher" <maxb AT ukf DOT net>
To: <cygwin AT cygwin DOT com>
References: <3DD4FCB5 DOT 5010800 AT umwelt-campus DOT de> <00c801c28caf$7439b6a0$78d96f83 AT pomello> <20021115153506 DOT GC2487 AT redhat DOT com>
Subject: Re: Problems with installer
Date: Fri, 15 Nov 2002 16:53:43 -0000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106

> On Fri, Nov 15, 2002 at 02:01:11PM -0000, Max Bowsher wrote:
>> Aargh! NetworkSimplicity SSH rears its ugly head once again.

Christopher Faylor <cgf AT redhat DOT com> wrote:
> I'm seriously beginning to think that setup.exe should detect
> a "NetworkSimplicity" installation and nuke it.  Seriously.

The thought had occurred to me too.

As far as I know, only 1 logic bug is the only remaining obstacle to a new
setup-snapshot, and then on to release.

Perhaps we should add a NetworkSimplicity check to this setup release?

Maybe not actually nuke it, but explain why it is bad.

Max.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/