munkiimport enhancement

2 views
Skip to first unread message

Gregory Neagle

unread,
Jul 13, 2026, 6:30:22 PM (15 hours ago) Jul 13
to munki-dev, munki-discuss
While out of town for MacAdmins at Penn State, my colleagues back in the office needed to add a new version of the Nuke apps to our Munki repo.

I’ve taught them how to use munkiimport, and they can successfully import packages, and disk images containing a package or an app, which covers 90%+ of the software we manage.

Unfortunately, The Foundry distributes Nuke on a disk image with a top-level folder containing mulitple apps. Normally, they way I import it is to use the -i/—item option to specify the top-level folder to be copied to /Applications, and then manually create the installs array. But helping my colleagues with that remotely was a bit confusing.

So I decided that I would, upon my return to the office, extend the munkiimport tool to handle situations like this.

When processing a disk image, if there is no package or application at the top-level, it will look for a top-level folder containing one or more applications. It should then create a pkginfo file containing an items_to_copy array to copy the folder to /Applications, and an installs array containing info for each application inside the folder. The minimum_os_version will take into account the required os version for all the apps in the folder. The version will be the highest version of all the apps in the folder (this is sort of an arbitrary choice, but there’s no generic way to determine which app’s version to use when there are multiple apps).

The resulting pkginfo may still need some manual editing, but it will be far less than that needed previously.

This will probably make it into Munki 7.3, but can be previewed from the Munki7dev branch.

-Greg
Reply all
Reply to author
Forward
0 new messages