Automating setup - --no-verify doesn't seem to work

Automating setup - --no-verify doesn't seem to work

[Andrew DeFaria]

I'm trying to automate the setup of cygwin and I'm running setup.exe 
with many additional options. All in all it's working fairly nicely but 
the --no-verify doesn't seem to work. The help says that --no-verify is 
"Don't verify setup.ini signatures" yet when I run it I see a lot of 
"Checking MD5 for <package>". Isn't there an option to turn off this MD5 
checking?
-- 
Andrew DeFaria <http://defaria.com>
Yes, I guess, they oughtta name a drink after you. - John Prine


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

Re: Automating setup - --no-verify doesn't seem to work

[Dave Korn]

On 24/02/2012 19:56, Andrew DeFaria wrote:
> I'm trying to automate the setup of cygwin and I'm running setup.exe
> with many additional options. All in all it's working fairly nicely but
> the --no-verify doesn't seem to work. The help says that --no-verify is
> "Don't verify setup.ini signatures" yet when I run it I see a lot of
> "Checking MD5 for <package>". Isn't there an option to turn off this MD5
> checking?

  No, those are actually two separate things.  The --no-verify option means
that setup.exe will accept any setup.ini file with any values for the md5sums
for packages, not just the official version; it doesn't stop the md5sums from
being checked, just means that a custom mirror can supply its own versions of
packages with their own md5sums, but they always get checked no matter what.

    cheers,
      DaveK

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