When building packages from a package source using Composer, there are two different types of packages: the PKG and the DMG.Do you know the difference between the two? And how to choose between them?
Each format has its own advantages depending on the intended use of the package and the tools used to deploy it. Let’s take a look at the differences and uses of the PKG and DMG formats.
PKG format packages can be deployed using virtually any tool, such as Apple Remote Desktop, Jamf Pro, or other client management systems. the PKG format is very easy to install, just double-click on the package to open it and enter the installer, and then follow the installation instructions to complete the installation. the PKG format packages not only provide a simple installation process, but also have pre-built scripts that are executed during the installation. The PKG package not only provides a simple installation process, but also allows you to execute pre-built scripts during the installation process, such as checking the installation environment, prompting for software that needs to be closed, uninstalling old versions of software, and so on. Please refer to the link provided on how to add scripts to the package source.
DMG format packages cannot be used on their own like PKG format packages, when used in conjunction with Jamf Pro the DMG format allows you to dynamically deploy files or folders to each user who has an account on the computer, as well as to the currently logged in network user account. In addition to this, you can deploy files or folders to system user templates, ensuring that any new user will receive the correct default environment.
I’m sure you’ll be able to understand the difference and make an appropriate choice after the above introduction.
PKG
– Stand-alone and easy to install
– Scripts can be added and executed
DMG
– DMG cannot be used alone, it needs to be combined with Jamf Pro.
– Can dynamically deploy files or folders
Add scripts to package sources:
https://docs.jamf.com/10.12.0/jamf-pro/administrator-guide/Adding_Scripts_to_Package_Sources.html