- #COMPATIBILITY PRO TOOLS 12.7 AND OS 10.12 INSTALL#
- #COMPATIBILITY PRO TOOLS 12.7 AND OS 10.12 DRIVER#
- #COMPATIBILITY PRO TOOLS 12.7 AND OS 10.12 PATCH#
If the installed macOS version is not in the list, the script returns an exit status of 1 and does not continue to install the software ( click here for that code excerpt).
To work around this, I utilize a preinstall_script to check for specific OS versions. jss recipe could define a policy with these specific versions in the os_requirements variable ( example here), but unfortunately we don’t have that option within a munki item’s pkginfo file. Given that munki only defines a supported OS range, there’s some extra work that needs to be done to help ensure that only Macs running one of the supported OS releases are able to install Pro Tools. This isn’t 100% required however, as you’ll see in a moment. Though only specific versions are supported (as of this writing, 10.13.6, 10.14.6, 10.15.3, and 10.15.5) defining the upper and lower boundaries is helpful for preventing munki from downloading the installer at all for incompatible OSs. This is subject to change, and requires referring to this Avid KB article. Second, we define the minimum and maximum OS versions in the pkginfo input dictionary. The only difference between the recipes is that with Pro Tools given the downloaded DMG contains the version in the filename, I use the collected found_filename variable collected by FileFinder to extract this version with the shared VersionSplitter processor: pkg recipes to handle finding the appropriate PKG within the larger DMG, verifying the expected certificate authority names, and copying the PKG out of the DMG for easier processing later. To make this extensible for other admins beyond my intended. Since these items are located within the same DMG file, all applicable recipes can use this one file for processing.pkg Recipes
#COMPATIBILITY PRO TOOLS 12.7 AND OS 10.12 PATCH#
As a result, the only real challenge is associating the specific component versions with the specific Pro Tools release to ensure that if a patch is available these are also installed (if needed). Additionally, all receipts and software are properly versioned. Unlike with my previous posts in this series, the main Pro Tools software and its component parts are all distributed as PKGs within the same, single DMG.
TL DR – you can reassign any collected autopkg output variable to any other desired variable for later use.
#COMPATIBILITY PRO TOOLS 12.7 AND OS 10.12 DRIVER#
The core question then was using the available processors, could I create the necessary Pro Tools munki item while simultaneous making the applicable Codecs and HD Driver versions a part of the item’s requires array? These supporting installs are tied to the specific Pro Tools release and which must be installed before Pro Tools. The challenge with automating this task is that any given release includes in the downloaded DMG the Pro Tools install as a PKG as well as both the required Codecs and HD Driver PKG installers. In this third part, my focus is on Pro Tools. In previous posts ( macOS erase & install, Autodesk Maya), I discussed how I created recipes for importing different software titles that I’d previously processed manually.
0 kommentar(er)
