X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=BAYES_00,SPF_HELO_PASS X-Spam-Check-By: sourceware.org Message-ID: <4B8693FA.90009@univ-paris1.fr> Date: Thu, 25 Feb 2010 16:15:06 +0100 From: Nicolas Cuissard User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Cygwin 1.7 deployment : disabling MD5 check? Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-up1-MailScanner-Information: Please contact crir .at. univ-paris1.fr for more information X-up1-MailScanner: Found to be clean X-up1-MailScanner-From: cuissard AT univ-paris1 DOT fr Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Hello, I'm on the edge of massively deploying Cygwin 1.7 from Cygwin 1.5 (+400 workstations), and I'm concerned about the time setup.exe takes to verify MD5 packages signature. When the repository is a remote SaMBa share, it looks that setup.exe download all packages one time to check the signature and another time to install the package. Is there a possibly to disable this check? As a workaround, I can silently synchronize the repository on the local drive and launching the setup from there, but it's more complicated that using a single repository on the network. Regards, -- Nicolas -- Ce message a ete verifie par MailScanner pour des virus ou des polluriels et rien de suspect n'a ete trouve. -- 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