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
Delivered-To: mailing list cygwin AT cygwin DOT com
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Subject: RE: cygwin.com suggestions
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
Date: Fri, 15 Mar 2002 17:38:17 +1100
Message-ID: <FC169E059D1A0442A04C40F86D9BA760014BC4@itdomain003.itdomain.net.au>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: cygwin.com suggestions
Thread-Index: AcHL6nd1ieirHv3GSNismOvM5TH5cQAAT9Vg
From: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To: <felixmendelssohnn AT mail DOT earthlink DOT net>, <cygwin AT cygwin DOT com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g2F6cvx24918

> -----Original Message-----
> From: felixmendelssohnn AT mail DOT earthlink DOT net 
> 
> Here are a couple of suggestions for making the cygwin.com 
> website more 
> helpful.

Thanks for your suggestions, feedback on them in-line.
 
> 1) Include the current version number of setup.exe on the front page. 
> Otherwise, there is no way for the infrequent visitor to the 
> website to 
> know if setup.exe has been updated other than to re-download 
> and run it.

Setup.exe will warn you if it is out of date - the online data includes
the current version of setup.exe in the ini file. Having the version
number on the website is thus redudant.
 
> 2) Include in the FAQ (or somewhere) a section on "How to 
> Safely Update the 
> Cygwin dll". Probably just "shut down all cygwin apps, 
> including daemons", 
> but it would be useful to know for sure.

The next release of setup.exe automatically address's this and will
replace in-use .dll's.
 
> 3) Include or link those instructions in announcements of new 
> Cygwin dll 
> releases.
> 
> Do these make sense?

They do, but as you can see we already have in place other measures to
address the same issues. 

Rob

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