This is the mail archive of the cygwin@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: setup.exe and "in-use-file"


Sven Köhler wrote:

i know that this feature has been requested many many times!

I don't know that. In fact, I can't recall this specific popup window EVER being requested, except as a possible proposal to solve a problem (but the problem was solved using a different method): There was some discussion about the problems setup PREVIOUSLY had updating a system when cygwin progs were running, and various solutions were proposed at that time. One of the proposed solutions was to do the popup thing as you descibe; another proposed solution was to use the standard Windows method of replacing in-use files: schedule them to be replaced on next-reboot, and ask the user "ok to reboot?" at setup's conclusion. The latter solution was chosen.


After implementing one solution to any problem, it is generally assumed that the other proposed solutions are null-and-void -- because the problem is solved.

Now, "I don't like the solution as implemented so please also implement this other solution" is a totally separate thing. And I do not recall anybody ever making that request -- AFTER the replace-on-reboot functionality was added to setup.

the more i wonder, why it hasn't been done yet :-(

<smartass>because nobody has requested it, after the underlying problem was solved using a different method (replace on reboot)</smartass>


Seriously, please provide links to the "many requests" for this specific behavior -- and exclude any from prior to the addition of replace-on-reboot capability to setup.

The real reason why this particular request has not been acted upon (if indeed it was requested post-replace-on-reboot) is the same reason any other request (fictional or not) lies dormant: we do not have infinite time nor an infinite number of programmers. We prioritize. If this particular itch is really bothering you, scratch it: write code, submit patches, etc. Otherwise, stop complaining or we'll be forced to refund your entire purchase price of the product.

Oh...right...

--Chuck



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]