FEATURE REQUEST: Disable "stop" button during check phase

[GoogleCodeExporter]

What steps will reproduce the problem?

1. Run Managed Software Update.app
2. It will start checking for updates, click the stop button right away.
3. You'll find that it quits what it was doing and thus doesn't display 
available updates.

Feature request:

I think it would be a very nice feature if you're able to disable the "stop" 
button during the check phase, much like you're able to do the same for the 
installation phase in the ManagedInstalls.plist.

Original issue reported on code.google.com by pleh.i...@gmail.com on 12 Jan 2011 at 2:51

[GoogleCodeExporter]

I'm not sure I understand the thinking here. munki checks for updates 
automatically in the background without user awareness or intervention. When 
the user manually launches Managed Software Update.app, they are indicating 
that they'd like to manually check for updates.  Why would we then prevent them 
from changing their mind and canceling the check by clicking the Stop button?

Original comment by gregnea...@mac.com on 12 Jan 2011 at 3:05

[GoogleCodeExporter]

Original comment by gregnea...@mac.com on 12 Jan 2011 at 3:05

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

I'm afraid this is my ignorance talking. (sorry for that)

During my testing I did allot of tests by manually starting the Managed 
Software Update.app and thus assumed the "check" part was visible for users at 
all times even when it's launched automatically.

But I realize now that this isn't the case and that users are simply prompted 
with their updates without seeing the "check" phase.

So in that respect your absolutely right that adding such a feature isn't 
really functional. (this request can be dismissed)

On a different note though (off topic), I do have another question. I noticed 
that users either get to see Apple updates or updates from the Munki repository 
but never both at the same time.

It seems that it runs a check list and displays whatever it finds first where 
updates from the Munki repository are shown first and Apple updates are only 
shown after Munki updates are installed.

Is this as intended? Or is it something that will be worked on in the future? 
(or am I missing something in my config)

Original comment by pleh.i...@gmail.com on 13 Jan 2011 at 7:50

[GoogleCodeExporter]

It behaves as intended. See the wiki doc AppleSoftwareUpdatesWithMunki. If 
you'd like to discuss this further, please ask on the munki-dev list, where 
more people can benefit from the discussion.

Original comment by gregnea...@mac.com on 13 Jan 2011 at 2:24

[GoogleCodeExporter]

Will do, thanks for the info.

Original comment by pleh.i...@gmail.com on 13 Jan 2011 at 2:29

[GoogleCodeExporter]

Closing issue for now.

Original comment by gregnea...@mac.com on 15 Jan 2011 at 3:29

• Changed state: WontFix