X-Spam-Check-By: sourceware.org To: cygwin@cygwin.com Subject: Re: MD5s of setup.exe on mirrors. References: <5qd5179mvu.fsf@hod.lan.m-e-leypold.de> <4644CB03.9070707@determina.com> <063001c7947a$3312cea0$2e08a8c0@CAM.ARTIMI.COM> <46461FA2.E6EFA773@dessent.net> <20070513161110.GA5651@ednor.casa.cgf.cx> <46489A67.7090503@determina.com> <4648A523.1010705@cygwin.com> From: "Markus E.L." Date: Mon, 14 May 2007 22:27:09 +0200 In-Reply-To: <4648A523.1010705@cygwin.com> (Larry Hall's message of "Mon, 14 May 2007 14:06:27 -0400") Message-ID: <5mabw7gnhe.fsf@hod.lan.m-e-leypold.de> User-Agent: Some cool user agent (SCUG) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com "LarryHall(Cygwin)" writes: > Alexander Sotirov wrote: >> Christopher Faylor wrote: >>> It was actually all academic before since: 1) there was nothing wrong >>> with the setup.exe on the mirrors and 2) people shouldn't have been >>> running setup.exe from the mirrors to begin with. >> >> Can you elaborate on why people shouldn't run setup.exe from the mirrors? I >> don't see what is the difference between setup.exe and the other packages. If >> you trust the mirror for all other binaries, why don't you trust it for setup.exe? > > Propagation time delays would be one reason. Since it's easy to grab > 'setup.exe' from the source, there's no sense using one that might be > dated. setup.exe is/was almost two years old. It doesn't seem to change too often. Did you mean setup.ini instead? But setup.ini is coming from the mirror, isn't it? (And this is a serious question: If it comes from the mirror, what happens if a mirror has setup.ini updated, but not all of the packages yet?) Regards -- Markus -- 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/