X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.8 required=5.0	tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <4C76A0A3.7030308@cwilson.fastmail.fm>
References: <4C768951 DOT 5010403 AT freesbee DOT fr>	<AANLkTi=oZq4gWna+8Bc+uuGqFJuuiyM-gg6CH7yWjfT0 AT mail DOT gmail DOT com>	<4C76A0A3 DOT 7030308 AT cwilson DOT fastmail DOT fm>
Date: Thu, 26 Aug 2010 18:23:24 +0100
Message-ID: <AANLkTinKCaCRpQp9MdcwWezXGbHC0NsyC6T6gmu6qsgb@mail.gmail.com>
Subject: Re: mintty start menu icon
From: Andy Koppe <andy DOT koppe AT gmail DOT com>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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

On 26 August 2010 18:13, Charles Wilson wrote:
> On 8/26/2010 1:07 PM, Andy Koppe wrote:
>>
>> 2010/8/26 Vincent Rivi=C3=A8re:
>>>
>>> It would be nice if the mintty package could honor the unchecking of "A=
dd
>>> icon to Start Menu"
>>
>> Yes, that would be nice, but unfortunately setup.exe's design doesn't
>> allow for this. The start menu icon is created by the mintty
>> postinstall script, which is run before the user even gets to the "Add
>> icon to Start Menu" option. Same issue for other packages that create
>> start menu entries.
>
> Would it be reasonable to move that dialog (sans the "Finished" wording, =
of
> course) earlier in the process -- and then export the value of those
> checkboxes via env vars like your other patch?

Yes, I think that would make sense, but I'm sure setup.exe would have
some interesting complications up its sleeve. We'd also need a new
final page. Perhaps the postinstall results page could be adapted to
serve in that role.

Quite a lot of work though for what's not exactly a critical issue.

Andy

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