X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Tue, 9 Feb 2010 11:49:16 -0500
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Wrong setup.exe on http://www.cygwin.com/
Message-ID: <20100209164916.GB18306@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <1265668504 DOT 29489 DOT ezmlm AT cygwin DOT com>  <Pine DOT LNX DOT 4 DOT 58 DOT 1002091114170 DOT 10309 AT mail3 DOT jubileegroup DOT co DOT uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.58.1002091114170.10309@mail3.jubileegroup.co.uk>
User-Agent: Mutt/1.5.20 (2009-06-14)
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 Tue, Feb 09, 2010 at 11:21:56AM +0000, G.W. Haywood wrote:
>Hello yet again,
>
>On Mon, 8 Feb 2010 Christopher Faylor wrote:
>> On Mon, Feb 08, 2010 at 09:21:30AM +0000, G.W. Haywood wrote:
>> >On Mon, 8 Feb 2010 Dave Korn wrote:
>> >
>> >>   These both work:
>> >>
>> >> http://www.cygwin.com/setup.exe?&go_away_proxy!
>> >> http://www.cygwin.com/setup.exe?go_away_proxy!
>> >
>> >This could work too:
>> >
>> >http://www.cygwin.com/setup-1.7.1-1.exe
>>
>> No.  It couldn't.  The first time setup-1.7.1-1 was updated you'd see
>> this same critical problem.  The situation here is that I have been
>> updating setup.exe to fix bugs and people are amazed and confounded by
>> the behavior of their proxy caches which don't retrieve the new version.
>
>I know what the situation is, and I've been suggesting a way of
>improving it.
>
>> Changing the name doesn't help that in any way.
>
>[Sigh.]
>
>Yes it does, if you change it every time you update it.

Your suggestion was unclear.

So you're saying that we should change the setup available on the
website to 1.7.1-1, 1.7.1-2, etc.  and possibly when a new Cygwin is
released: 1.7.2-1.  Sounds like a lot of extra work to fix a "problem"
affecting a handful of people; especially when the majority of users
apparently have no problem just downloading the latest version.  It
sounds like this major change in behavior would trade a minor amount of
proxy cache confusion for a major amount "What happened to setup.exe?"
confusion.

Perhaps more importantly, with the possible exception of updating the
web site to allow hints that setup.exe shouldn't be cached, I don't
believe that there is a problem here which requires a change.  So there
is not going to be a change in the name of setup.exe.

cgf

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