You can easily convert a Composer generated installer dmg to a standard pkg with these commands:ġ) mount the dmg: $ hdiutil attach /path/to/Sample.dmg
Since the Composer generated dmgs contain all the files for the payload in the proper folder structure you can just use the entire mounted volume as your payload root for pkgbuild. However, in some cases that might not be possible or necessary. In general, it is probably preferable to re-visit your imaging process and rebuild any installer you still may have in dmg format from scratch. I cover many of them in my book: Packaging for Apple Administrators Luckily there are plenty of great other third-party tools to build installer packages. Also the Composer application is 32-bit and its future is uncertain. However, Jamf themselves have been recommending to use the standard pkg format in favor of their proprietary use of dmg.
There are certain features in Jamf Pro which can install and distribute files to user directories and templates (called ‘Fill User Templates’ FUT and ‘Fill Every User’ FEU) which only work with dmg installers in Jamf Pro.
#MAC, CONVERT APP TO DMG HOW TO#
The Jamf Pro management system how ever will understand what to do and how to install the files from the dmg to a system. On its own, however, this dmg cannot do anything.
The dmg option will build a standard dmg disk image file, with the payload of the installer as contents. The pkg option will build a standard pkg installer file, which will install with any system that can install pkg files. The standard pkg and the seemlingly standard (but not) dmg. Jamf Composer has always had two formats to build installers.
0 kommentar(er)
