We always push sample library package first, then the settings package, then the. As you said the sample libraries are over 60Gb. 3 controlled which packages go down in what order. Some, if not all settings dont conform to standard plist or simple text settings. app refused to be indexed by jamf admin no matter how many times one re-opened jamf admin and tried again. app, the settings, and the sample sounds. We devide the whole installation into 3 packages. you simply have to figure out where Ableton is downloading the packages temporarily to. I would not recommend using the technique for that purpose anymore because there are better ways to deploy App Store packages however the technique is solid. Here’s an old post from Rich Trouton describing how to use this very technique to get packages out of the Mac App Store. Once you figure out exactly what it’s doing and where, you could copy or “hard link” the temporary package somewhere and then you’d have a copy. I know of quite a few large software packages that use that very technique. My uneducated wager (no firsthand experience with Ableton Live) is that it is bringing pkg files to a temp directory somewhere and then quietly installing them. If it is a downloaded pkg file then your installer log would have a record. Also if I were you I would look in your package receipts and your log files on macOS in /Application/Utilities/Console.app while the package is installing. I don’t recommend using Composer to repackage, but I do use it to study where the software is putting stuff on my test Macs and VMs.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |