X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,SARE_WEOFFER
X-Spam-Check-By:	sourceware.org
From:	"Jason Pyeron" <jpyeron AT pdinc DOT us>
To:	<cygwin AT cygwin DOT com>
References:	<1268526388 DOT 20918 DOT ezmlm AT cygwin DOT com> <Pine DOT LNX DOT 4 DOT 58 DOT 1003141111350 DOT 14642 AT mail3 DOT jubileegroup DOT co DOT uk> <20100314163002 DOT GA12172 AT ednor DOT casa DOT cgf DOT cx>
Subject:	RE: incomplete/corrupted setup.exe
Date:	Sun, 14 Mar 2010 13:05:23 -0400
Message-ID:	<03988E63C1BD48809EA3A27E4D6A3661@phoenix>
MIME-Version:	1.0
In-Reply-To:	<20100314163002.GA12172@ednor.casa.cgf.cx>
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
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

 

> -----Original Message-----
> From: Christopher Faylor
> Sent: Sunday, March 14, 2010 12:30
> Subject: Re: incomplete/corrupted setup.exe
> 
> On Sun, Mar 14, 2010 at 11:12:42AM +0000, G.W. Haywood wrote:
> >Hi there,
> >
> >Fifteen messages on this subject and counting.
> >
> >How long would it take just to install a temporary symlink 
> for the guy?
> >
> >Something like
> >
> >cygwin-setup-1.7-2010.03.14.exe
> 
> You aren't thinking about the consequences of your 
> suggestion.  It would not scale.  What happens the next time 
> there is a setup.exe update?  We update the symlink too?  And 
> if someone stops allowing the symlinked URL we create a new 
> one?  Do we need to keep the symlink around forever just for 
> this one person?  Do we offer this service to anyone who 
> can't download?

While I agree whole heartedly, I do think the current naming scheme does have
its draw backs, and that it could out weigh the benefits of not changing.

Here is the proposal:

Name setup.exe as cygwin-setup-v.vv.vv.exe or similar meaning and continue to
provide setup.exe as the most current cygwin-setup-v.vv.vv.exe (by symlink or
redirect)

Just a few points to justify:

* Know which version of setup is being used.
* Know which program's setup is sitting on the desktop (or other lint collection
place)
* Avoid stupid heuristics matching base on file name (At the Navy Cygwin is
allowed but no one is allowed to execute files matching "setup.exe" but
cygwin.exe, sadasdasdfsa.exe or almost anything else is allowed.)
* Change management, that a user can observe.

A point against changing:

* No new effort

> 
> And, most importantly, WJM.
> 

I like mean.


--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
-                                                               -
- Jason Pyeron                      PD Inc. http://www.pdinc.us -
- Principal Consultant              10 West 24th Street #100    -
- +1 (443) 269-1555 x333            Baltimore, Maryland 21218   -
-                                                               -
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
This message is copyright PD Inc, subject to license 20080407P00.


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

- Raw text -