tips in installing and packaging Cocoa

casareanderson
New Contributor III

Hi i am trying to set up patchoo but i having issues installing and packing cocoa dialog has any one got any tips on doing this

1 ACCEPTED SOLUTION

mm2270
Legendary Contributor III

There isn't too much of a trick to packaging and deploying it.
Step 1 is, you need to choose a location for cocoaDialog to go in. For example, some folks like to just put it right in /Applications/Utilities/ Some, like us, prefer to tuck it away into a more hidden location, like /Library/Application Support/JAMF/bin/ And there are lots of other places it can go. It just needs to be in a location that will be common across all your Macs.

Wherever you decide it should go, Step 2 is to copy it using any method that works for you into that location of your choice on a Mac that has Composer.app on it.

Step 3 is: Open Composer and click Cancel if it asks you to choose a type of package to create. Drag cocoaDialog into the Composer sidebar to create a new source. The folder structure its in will also be copied in, but, you should end up only with folders and cocoaDialog in its final location in the source. If there's anything in there that doesn't belong there, delete it from the Composer source.

Step 4 is to adjust any permissions and ownership on cocoaDialog within Composer. Normally you don't want it owned by any regular account. Its a good idea to make it owned by root but give full read permissions to all accounts the entire bundle.

Once all that's done, build your package. Your choice on whether to use a DMG or pkg format. Either should be fine.

That's basically it. Upload the final package into your Casper Admin share and run some test policies to install it to make sure its working as expected and you can call it up in a script.

View solution in original post

2 REPLIES 2

mm2270
Legendary Contributor III

There isn't too much of a trick to packaging and deploying it.
Step 1 is, you need to choose a location for cocoaDialog to go in. For example, some folks like to just put it right in /Applications/Utilities/ Some, like us, prefer to tuck it away into a more hidden location, like /Library/Application Support/JAMF/bin/ And there are lots of other places it can go. It just needs to be in a location that will be common across all your Macs.

Wherever you decide it should go, Step 2 is to copy it using any method that works for you into that location of your choice on a Mac that has Composer.app on it.

Step 3 is: Open Composer and click Cancel if it asks you to choose a type of package to create. Drag cocoaDialog into the Composer sidebar to create a new source. The folder structure its in will also be copied in, but, you should end up only with folders and cocoaDialog in its final location in the source. If there's anything in there that doesn't belong there, delete it from the Composer source.

Step 4 is to adjust any permissions and ownership on cocoaDialog within Composer. Normally you don't want it owned by any regular account. Its a good idea to make it owned by root but give full read permissions to all accounts the entire bundle.

Once all that's done, build your package. Your choice on whether to use a DMG or pkg format. Either should be fine.

That's basically it. Upload the final package into your Casper Admin share and run some test policies to install it to make sure its working as expected and you can call it up in a script.

casareanderson
New Contributor III

thank you @mm2270