> On Aug 6, 2020, at 1:42 PM, Jason Liu <jason...@umich.edu> wrote: > > All that said, one more question. As I now understand it, the idea is to > download a binary-only installer (from the publisher’s web site) and launch > it. Someone still has to answer any and all dialogs that such installers > always present. So, it fact, the administrator has to sit at the machine and > click “OK” ad nauseam. Previously, I thought we were going to create a new > binary image that would avoid such tedium. Do I have this right? Or is > there some scripting trickery wrapped around the installer? > > The situation of dialog boxes and clicking "OK" ad nauseam is, in most cases, > completely unnecessary. Installing binary-only installers (.dmg or .pkg) can > be accomplished exclusively using the command line: > > If the installer is a .dmg: > > # hdiutil mount software-title.dmg > > Once the DMG is mounted, if it's just the app, then > > # cp -R "/Volumes/Mounted DMG/Software Title.app" /Applications > > on the other hand, if the contents are a .pkg, then > > # /usr/bin/installer -package "/Volumes/Mounted DMG/Software Installer.pkg" > -target "/Volumes/Macintosh HD" > > Finally, unmount the DMG: > > # hdiutil unmount "/Volumes/Mounted DMG" > > For the vast majority of cases, no manual user intervention is necessary. In > fact, software deployment tools such as Jamf/Casper, Munki, and even Apple > MDM, use this method to perform non-interactive remote installations of Mac > software. > > —
MacPorts can do much of this automatically, I belive: <https://github.com/macports/macports-base/blob/0b8b970a857c611a3c8aea8385b3ea28ce38e2c9/src/port1.0/portextract.tcl#L117> Ken
