According to Christopher Faylor on 1/10/2010 12:27 PM: > This idea has been put forth many times since that time. The fact that > it isn't implemented means that either 1) It's more difficult than you > anticipate or 2) No one thinks its a good idea.
And here's one reason why. Newer versions of cygwin1.dll introduce new entry points. But suppose you are updating cygwin1.dll and bash at the same time. If the new bash depends on one of those new entry points, but the old cygwin1.dll is still in operation, then the replace-on-reboot won't save the fact that the new bash won't work until the reboot. Really, it is better to stop ALL things cygwin, do the upgrade, and not worry about those interactions. -- Don't work too hard, make some time for fun as well! Eric Blake e...@byu.net
signature.asc
Description: OpenPGP digital signature
