We're preparing to release an option SupportMenu item, managed via /Library/LaunchAgent. It'll be enabled for a computer, or disabled, as our Subscriber chooses.
Im trying to figure … what's the less of all evils:
- Distributing the LaunchAgent as Disabled, then having the postflight set the Disabled key to False as required.
or
- omitting it from the BOM and having the postflight copy it into place as required.
It's not the worst abuse of the "package, don't write" guideline, but still, if I can avoid it, I'd like to.
Is there another option, outside of having two versions of the installer?
I suppose I could have the Menu Item look for a key, and launchctl unload itself , but then the app opens for a moment at every login.. seems worst of all these options….
Thanks in advance for any options I'm not seeing.
--
Allen Hancock - Watchman Monitoring - A consultant's best friend
+1-408-352-6145
|