setup.exe --quiet-mode

[Brian Dessent]

Christopher Faylor wrote:

> Dave did suggest a possible workaround - delay any postinstall scripts
> until the next reboot.

That's more graceful than requiring the user to re-run setup to catch
the failed postinstalls.  But it still results in a broken system until
the next reboot since those binaries that were just installed will all
fail if you try to run them.  (And if they don't fail because of missing
entry points, they could fail because their postinstalls were
deferred.)  That's what I mean by "no workaround" -- the immediate
result after running setup with cygwin1.dll in use is a broken system,
and there's not a lot you can do to avoid that other than "don't run
setup with important DLLs in use".

Brian

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