X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Sun, 14 Mar 2010 12:30:02 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: incomplete/corrupted setup.exe Message-ID: <20100314163002.GA12172@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <1268526388 DOT 20918 DOT ezmlm AT cygwin DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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: List-Unsubscribe: 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 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? Plus, the way to fix a problem is to fix the problem not kludge around it. There was something wrong on the OP's end. Finding out what was wrong and fixing the problem is the way to make sure it won't happen again. There is no guarantee that creating a symlink would do that (and judging by followon mail it probably wouldn't). And, most importantly, WJM. 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