Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <42F6A087.A111B257@dessent.net> Date: Sun, 07 Aug 2005 17:00:07 -0700 From: Brian Dessent MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: setup.exe filename References: <200508072325 DOT j77NPfP22698 AT ns DOT pyerotechnics DOT com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Report: -5.7/5.0 ---- Start SpamAssassin results * -3.3 ALL_TRUSTED Did not pass through any untrusted hosts * -2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1% * [score: 0.0000] * 0.2 AWL AWL: From: address is in the auto white-list ---- End SpamAssassin results X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com Jason Pyeron wrote: > I like typing start->run http://cygwin.com/setup.exe, as I am sure most of > us do. But it would be a "best" practice to name the installer, something > descriptive, like cygwin-2.457.2.2.exe. I do not like the idea of adding the version to the name of the file. To a naive user it would reinforce the incorrect idea that the version of setup has anything whatsoever to do with the version of Cygwin and other packages that they are installing. We already get too many of those on the mailing list as it is. A user might see "setup-1.2.3" and then later see "setup-1.3.4" and think, "oh look it's a newer version of Cygwin." Or, they would look at the version of setup.exe and not bother taking any action if it's the same as the one they already have, even though dozens of packages may have been updated meanwhile. Quite frankly the version of setup.exe is next to irrelevent as long as it's somewhat recent, barring any specific bug that the user might be running into. And the setup.ini is versioned so that if you try to use an older setup.exe than what is current you will get a warning. As far as renaming it to something like "cygwin-setup.exe" or "cygsetup.exe" or whatever, I'm neutral. I do think it's unfortunate that it has always been named a generic word, but I think changing it now would cause more confusion than good. Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/