Now that I’ve got SD working (thanks!) I’m trying to figure out the best way to use it.
Generally I want to share with users Apple Applets, Enhanced applets and script libraries, along with various files and folders.
I group several apps that work on related tasks in the same folder on the user’s HD.
(Not the application’s folder.)
What I would like to do is notarize all of the apps, include various libraries (my own and Shane’s and others) in an installer that creates a folder in the user’s home folder (or updates the current one) and puts all the apps there and the scrip libraries in the user’s script library folder (if current versions are not already there). (Or, I guess I could put a copy of each library in each app, but that seems redundant).
I have DropDMG, and an image would be, but I’m hoping to include all the needed tools for a particular task.
One thought is to notarize all the apps, put them in another app that works as an installer.
I don’t know if this relevant or not, but I use DMGCanvas to create and notarize disk images that contain apps and installer apps. I’ve always notarized the apps separately, but their web site says that the app will notarize the apps and their contents, so it should be possible to use this without also using SD Notary (I’ll try doing that next time I use the app.) It costs money, but I’ve always found it worthwhile.
Put all the folders, files, scripts (for the scripts menu), libraries and notarized apps inside an installer app.
Notarize the installer app and distribute that.
When the installer app runs it will copy all its contents into the right places, including putting the libraries in the user library folder and the scripts in the user scripts folder.
As I said above, I’d look to zip the enclosed apps, to make sure no contents get changed in notarizing the installer. SD Notarry can only discern so much of your intent.
No.
Apple’s developer documentation. Apart from the one required for third-party ASObjC libraries, you’re unlikely to need them.
They’re fine – as long as they never modify themselves (or get modified by a user). In practice, the best way to ensure that is to export run-only versions.