This is the plist file that Logic supposedly uses to know what to download. Use the above info to write an Autopkg list.Document the installs list data with the associated pkg download link.This will output the installs list info you need for the Munki pkginfo copy that path and run /usr/local/munki/makepkginfo -f against it. command+i will show you the path to this file.Pkg by pkg open the package in Pacifist and expand the file tree to file the first file and it's location.Once the packages are safely copied complete the Logic Installation of the pkgs.Download all the packages viaa fresh Logic Install and obtain them (before installing) via this method:.The resaon for the above is that so far Munki has been trying to reinstall the pkgs unless there is a an installs entry. From the files installed by the pkg a file needs to be chosen to run /usr/local/munki/makepkginfo -f /path/to/file against in order to generate items for an installs list to be added to each pkginfo file.

The idea is to first document all the download links for each pkg. As this info is in the pkgs from apple it might be little trouble to add them anyway, but I have also been advised that if pkg receipts have not been working it's probably due to this bug: !topic/munki-dev/0Ku-dUjQooQ (There is discussion about updating munki in relation to dealing with this, but in the meantime it may have to be done manually if it cannot be scripted.)Īutopkg Recipes for downloading and importing Logic Pro X Additional Content into Munki. Originally too I thought that installs keys would be required. A better idea would be to extend Hannes' work: and add the functionality to push the packages to munki after downloading them. If the packages were being regulary updated then this might be a good idea but they are not.

UPDATE: Thanks to some good advice from Greg Neagle this is probably the wrong way to go about it.

Logic pro x download additional content