Jeremy Bopp writes: > BTW, this is not only a problem for the cygwin package. Literally any > package could have files which are in use at the time of replacement. > So any solution would need to take that into account.
True but sometimes the perfect is the enemy of the good enough... The 'cygwin' package is just about guaranteed to be in use if you are doing anything cygwin related. If you did the warning for this and maybe also bash (assuming it locks files) then you would cover the key issues. -- View this message in context: http://old.nabble.com/Suggestion%3A-Have-setup.exe-warn-before-upgrading-%27cgywin%27-package-itself-tp26327934p26328317.html Sent from the Cygwin list mailing list archive at Nabble.com. -- 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
