Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Message-ID:	<000601c0d972$76f63540$9332273f@ca.boeing.com>
From:	"Michael A. Chase" <mchase AT ix DOT netcom DOT com>
To:	<cygwin AT sources DOT redhat DOT com>
References:	<EA18B9FA0FE4194AA2B4CDB91F73C0EF08EFA8 AT itdomain002 DOT itdomain DOT net DOT au> <20010510005533 DOT A12859 AT redhat DOT com>
Subject:	Updating setup.exe
Date:	Thu, 10 May 2001 06:13:59 -0700
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE:	Produced By Microsoft MimeOLE V5.50.4133.2400

All the coming changes to setup.exe seem nice.  I have been building
periodically from source so I could try out the new features, but how will
ordinary users know to download the new version when it is released?

Perhaps there should be a setup or install 'package' that would allow
updating setup.exe to be controlled like any other part of Cygwin from the
user's viewpoint.  It would probably have to be a special case since I don't
think a running copy of setup.exe can replace itself.  It also probably
wouldn't be in the Cygwin directory tree.

If it sounds like a good idea to others, I am willing to work on the
mechanism as soon as my company signs its disclaimer for my contributions.
I have been told that there is no problem with the disclaimer, but it hasn't
been signed yet.
--
Mac :})
Give a hobbit a fish and he'll eat fish for a day.
Give a hobbit a ring and he'll eat fish for an age.



--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

- Raw text -