DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:from:date
	:message-id:subject:to:content-type; q=dns; s=default; b=g3urJYN
	FSZTVpVDNnJ2+L9F0gOFHu99H83bxe54IAyeKqyv9YVpnJ6z52bkudyLDbyIYsAY
	fO/U2yrdsutpiMRFhpHKadq1Q5nwN851C8aYrZrtXnxggCFB6q87fEne5NU41R2x
	0oFtor4H0F4bv0d+tV5Y8dTvcyblf8PAfdo4=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
MIME-Version: 1.0
In-Reply-To: <044562e5-6c8e-1649-0a48-0e486a098510@gmail.com>
References: <CAG-pUxkQ_iniFA0r9i2zkT1uFMEvCei0wc9rd45RBYj2uBnVhA@mail.gmail.com> <d7f8f9e5-e77d-8dde-8882-15084904cbe0@mitel.com> <CACoZoo0zFt++CnsXjvvG1rrAd3fdv2mBd9=pZiRcd6+1VDC3Eg@mail.gmail.com> <9d6c50f4-3759-0a45-a97c-30b031a906a0@SystematicSw.ab.ca> <CACoZoo3QQb751UVGiQSo1ArskXOpJR=xhn=zFPJwSreW7FYefA@mail.gmail.com> <1cdcdc17-200d-6ec1-66c5-894c0cf16937@gmail.com> <CACoZoo09=r6GS5q2uWUfooDH8s=NzoD1dhyK=JTY2XaCiYKCAA@mail.gmail.com> <044562e5-6c8e-1649-0a48-0e486a098510@gmail.com>
From: Erik Soderquist <ErikSoderquist@gmail.com>
Date: Wed, 14 Dec 2016 16:58:35 -0500
Message-ID: <CACoZoo3bafxrYNQn9_DpqEu7aqEomxZo+M-5sZ7Q8=UGCfAGhw@mail.gmail.com>
Subject: Re: Installer names not meaningful enough
To: cygwin@cygwin.com
Content-Type: text/plain; charset=UTF-8

On Wed, Dec 14, 2016 at 4:50 PM, cyg Simple <cygsimple@gmail.com> wrote:
> And if we were purely *nix your argument might hold merit but this setup
> executable provides a Windows OS based install of a Windows based
> application set known as Cygwin.

If we were purely *nix, we wouldn't be on Windows in the first place.

> The name of the executable has never been a problem; why are you trying
> to create one?  There are just as many that would keep it simple and
> leave the name as is.

I don't recall anyone trying to create a problem so much as find out
the reasoning behind the decision and ask for the setup executable
version information to be more accessible than it currently is.  At
present, it does not appear that the cygwin pages list the current
setup executable version at all, forcing either an aborted setup run
when the setup executable itself reports that the setup.ini file
indicates the currently running executable is outdated, or downloading
*something* to see if the version of setup available for download has
changed.

-- Erik

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