Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sources.redhat.com
Message-ID: <02ba01c16d4a$4d4835b0$0200a8c0@lifelesswks>
From: "Robert Collins" <robert.collins@itdomain.com.au>
To: "Robert Mecklenburg" <mecklen@cimsoft.com>, <cygwin@cygwin.com>
References: <200111140310.fAE3AOx02272@loony.cygnus.com> <15346.40869.254000.127663@gargle.gargle.HOWL>
Subject: Re: [ANNOUNCEMENT] Setup.exe Updated
Date: Thu, 15 Nov 2001 07:24:02 +1100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit


----- Original Message -----
From: "Robert Mecklenburg" <mecklen@cimsoft.com>
To: <cygwin@cygwin.com>
Sent: Thursday, November 15, 2001 3:45 AM
Subject: Re: [ANNOUNCEMENT] Setup.exe Updated


> RC> The long awaited setup.exe update has occured.
>
> Thank you for this excellent upgrade!  A trivial observation: when I
> got to the package selection dialog (I don't know it's official name)
> the text on the "View" button was corrupted (i.e., pixels scrambled).
> Clicking it refreshed properly and fix the problem.

Thats a known bug - discussed here about a week ago during the testing
spree. Patches gratefully accepted. (The scrambling is windows
'highlighting' the button).

> Question 1: The dialog box which offers to create an short cut and
> menu item has the boxes checked by default.  I've run previous
> versions of the setup tool many times (twice a week since the tool was
> released!) and always unchecked these boxes, but setup doesn't seem to
> remember my choice.  I would swear that others in my organization
> using the tool have these boxes unchecked (presumably because it
> remembered their previous choice).  So, I'm asking about the intended
> behavior - should setup remember the previous checked/unchecked status
> of the create short cut and create menu item boxes?

It should default to off, but I think the change from Cygnus to Cygwin
has confused it. Let it have it's way, and then it should be happy in
the future :}.

> Question 2: Would it make sense to have setup's source code
downloadable
> from the setup tool?  (Obviously, it would make less, no?, sense to be
> able to download setup.exe itself.)

The source is available as part of the "cygwin-src" tarball. It won't
build very happily outside that source tree, so having a separate
download doesn't make sense. In the future, when we can associate binary
packages with source tarballs, we will make such a link for convenience.

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/