3 ms·

The "please quit iTunes" thing happened to me with Xcode 4.0 on 10.6 as well. Pretty ridiculous.

• fredoliveira 15y ago
  The Xcode installation asks you to close iTunes because of iTuneshelper and how iTunes will sync devices (including development devices) when they're plugged in. It makes sense that Xcode asks you to quit itunes (and kills ituneshelper too) to update files. It isn't ridiculous.
  • deleted 15y ago
    [deleted]
  • epistasis 15y ago
    The broken application detection and the refusal to identify which processes need to be killed is ridiculous. Having a dev system that's so fragile that iTunes needs to killed when installing Xcode is insane. It's the request of a lazy programmer that's not willing to put in the work of understanding the real requirements or working around the problems, and would be unacceptable in a consumer-facing application. I don't want to say it's OK in the developer tools, but probably not as bad.
  • pornel 15y ago
    It is ridiculous, because: • asks user to perform task manually which is trivial to automate: `tell application iTunes to quit`. Apple even has sudden termination API that iTunes could use to make it safely killable most of the time. • needs to quit iTunes in the first place. Why can't it take advantage of versioning of libraries and frameworks? Why can't it update files in place? (running application should see old version [inode] until it closes the file). • and the usual ridicule: a music player is a critical piece of device sync and development infrastructure.