This ensures Casper has a receipt that follows your naming convention, by naming YOUR package using your company's package naming convention, for example vendor-application-version which would show up as "Installed by Casper": Using your favorite tool, drop the PKG/MPKG (or even the DMG) into /tmp and trigger it with the standard commands. Including (but not limited to) not renaming the original PKG/MPKG. These are the kind of clean PKG/MPKG installers we deploy with absolutely no modification. The litmus test would be to push to a freshly imaged Mac (virtual machine in ESXi or physical?) and circle back to see if any permissions got whacked (most mature tools default to NOT altering existing directory ownership/permissions), etc. Seems at first glance like a nicely designed package.
Here are screenshots of the Shockwave Flash installer. Pacifist is one of the most valuable tools for examining PKG/MPKG installers. Sudo rm -rf /Library/Application Support/Adobe/Shockwave 11Ĭould it be that Adobe's installer development team are maturing? :b If you open the full Shockwave PKG in Pacifist, you'll find there is only one preflight script containing simply: #! /bin/bash Anyone who thinks a snapshot is a smart way to deploy software that shipped with installers containing logic, well.I'll withold my snide remarks. Nothing makes me cringe more than "snapshots".to your point, there's a reason developers build logic into their PKG/MPKG installers.
0 kommentar(er)
