Assets/ scripts/ accept_zoom_license.sh configure_outlook_profile.py icons/ company_vpn.icns tools/ jq Once built, host the package on an internal web server or a Jamf distribution point. Then, in any AutoPkg recipe that needs those assets, add:
Here’s a draft feature article about autopkg-assets.pkg , written for a technical audience familiar with AutoPkg and macOS management. For years, AutoPkg has been the silent workhorse of macOS device management. It fetches, verifies, and repackages software, turning manual updates into automated workflows. But ask anyone who’s built a serious AutoPkg infrastructure, and they’ll eventually hit the same quiet frustration: where do you put the other files—the licensing scripts, custom icons, branding assets, or binary tools that make your packages deployment-ready? autopkg-assets.pkg
<key>Requires</key> <array> <string>com.yourorg.autopkg-assets</string> </array> Imagine you maintain a GoogleChrome.pkg recipe. Chrome requires no license acceptance, but your organization demands a post‑install script that disables automatic updates and writes a custom brand plist. Assets/ scripts/ accept_zoom_license
Without autopkg-assets.pkg , you’d have to fork the upstream recipe and embed your script—then rebase every time the parent recipe changes. Chrome requires no license acceptance, but your organization
pkgbuild --root ./Assets \ --identifier com.yourorg.autopkg-assets \ --version 1.2.0 \ --install-location /Library/AutoPkg/Assets \ autopkg-assets-1.2.0.pkg The Assets folder mirrors the final install location. For example: