Overall purpose was to improve the logging in the scripts. But the handling of macOS version and Installomator version in order to utilize swiftDialog has been improved, too.
`name` is now the name of the app. App has perfect values in it's version, so no need for `packageID`. Since `name` matches the name of the app, `blockingProcesses` comes for free.
IBM for some reason is adding too much to the “tag” on Github, so they have “Version 2.9.1 Build 96” for the current latest version. That ends up being read as 2.9.196, and not only 2.9.1 that the app version is.
I upload this, so we have it ready, but not sure if `appNewVersion` should stay or be commented out.
The developer has now also released an Apple Silicon version of the software, so a review of the processor and the appropriate download links have been added
The expectedTeamID is now a variable because the Apple Silicon version of the app has a different TeamID
Today something strange happened for Installomator on GitHub. Or latest release would spend too much time loading the assets, and would not return an URL, like here:
```
% gitusername="Installomator"; gitreponame="Installomator"; curl -sfL "https://github.com/$gitusername/$gitreponame/releases/latest" | tr '"' "\n" | grep -i "^/.*\/releases\/download\/.*\.pkg" | head -1
% gitusername="bartreardon"; gitreponame="swiftDialog"; curl -sfL "https://github.com/$gitusername/$gitreponame/releases/latest" | tr '"' "\n" | grep -i "^/.*\/releases\/download\/.*\.pkg" | head -1
/bartreardon/swiftDialog/releases/download/v1.11.2/dialog-1.11.2-3095.pkg
```
As can be seen above it worked for swiftDialog, but not for Installomator.
Now we can fall back on the API call if we do not get the URL in first try.
Servers has been changed, so various headers are needed to get the API to work.
Have tried this:
```
curl -H "accept: */*" -H "accept-encoding: gzip, deflate, br" -H "accept-language: en-US,en;q=0.9" -H "content-length: 30" -H "content-type: application/json" -H "origin: https://me-download.wickr.com" -H "referer: https://me-download.wickr.com/" -H "sec-fetch-dest: empty" -H "sec-fetch-mode: cors" -H "sec-fetch-site: same-origin" -H "sec-gpc: 1" -H "user-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/104.0.5112.102 Safari/537.36" "https://me-download.wickr.com/api/download"
```
Two different hosts for Me and Pro:
[https://me-download.wickr.com/](https://me-download.wickr.com/)
[https://pro-download.wickr.com/](https://pro-download.wickr.com/)
I have tried with Brave browser to detect what headers are needed to get the api to work, but it refuses.
Output:
```
# ./Installomator/utils/assemble.sh charles DEBUG=0
2022-08-25 13:31:09 : INFO : charles : setting variable from argument DEBUG=0
2022-08-25 13:31:09 : REQ : charles : ################## Start Installomator v. 10.0beta1, date 2022-08-25
2022-08-25 13:31:09 : INFO : charles : ################## Version: 10.0beta1
2022-08-25 13:31:10 : INFO : charles : ################## Date: 2022-08-25
2022-08-25 13:31:10 : INFO : charles : ################## charles
2022-08-25 13:31:10 : INFO : charles : SwiftDialog is not installed, clear cmd file var
2022-08-25 13:31:10 : INFO : charles : BLOCKING_PROCESS_ACTION=tell_user
2022-08-25 13:31:10 : INFO : charles : NOTIFY=success
2022-08-25 13:31:10 : INFO : charles : LOGGING=INFO
2022-08-25 13:31:10 : INFO : charles : LOGO=/System/Applications/App Store.app/Contents/Resources/AppIcon.icns
2022-08-25 13:31:10 : INFO : charles : Label type: dmg
2022-08-25 13:31:10 : INFO : charles : archiveName: Charles.dmg
2022-08-25 13:31:10 : INFO : charles : no blocking processes defined, using Charles as default
2022-08-25 13:31:10 : INFO : charles : name: Charles, appName: Charles.app
2022-08-25 13:31:10 : WARN : charles : No previous app found
2022-08-25 13:31:10 : WARN : charles : could not find Charles.app
2022-08-25 13:31:10 : INFO : charles : appversion:
2022-08-25 13:31:10 : INFO : charles : Latest version of Charles is 4.6.2
2022-08-25 13:31:10 : REQ : charles : Downloading https://www.charlesproxy.com/assets/release/4.6.2/charles-proxy-4.6.2.dmg to Charles.dmg
2022-08-25 13:31:32 : REQ : charles : no more blocking processes, continue with update
2022-08-25 13:31:32 : REQ : charles : Installing Charles
2022-08-25 13:31:32 : INFO : charles : Mounting /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/tmp.MO2B5ihQ/Charles.dmg
2022-08-25 13:31:37 : INFO : charles : Mounted: /Volumes/Charles Proxy v4.6.2
2022-08-25 13:31:37 : INFO : charles : Verifying: /Volumes/Charles Proxy v4.6.2/Charles.app
updateDialog:26: no such file or directory:
2022-08-25 13:31:45 : INFO : charles : Team ID matching: 9A5PCU4FSD (expected: 9A5PCU4FSD )
2022-08-25 13:31:45 : INFO : charles : Installing Charles version 4.6.2 on versionKey CFBundleShortVersionString.
2022-08-25 13:31:45 : INFO : charles : App has LSMinimumSystemVersion: 10.7
2022-08-25 13:31:45 : INFO : charles : Copy /Volumes/Charles Proxy v4.6.2/Charles.app to /Applications
2022-08-25 13:31:46 : WARN : charles : Changing owner to schwartzm
updateDialog:26: no such file or directory:
2022-08-25 13:31:46 : INFO : charles : Finishing...
2022-08-25 13:31:49 : INFO : charles : App(s) found: /Applications/Charles.app
2022-08-25 13:31:49 : INFO : charles : found app at /Applications/Charles.app, version 4.6.2, on versionKey CFBundleShortVersionString
2022-08-25 13:31:49 : REQ : charles : Installed Charles, version 4.6.2
2022-08-25 13:31:49 : INFO : charles : notifying
2022-08-25 13:31:49 : INFO : charles : App not closed, so no reopen.
2022-08-25 13:31:49 : REQ : charles : All done!
2022-08-25 13:31:49 : REQ : charles : ################## End Installomator, exit code 0
```
## Great solution for IdP Password Syncing by TwoCanoes!
XCreds works by keeping your local Mac password in sync with your Identity Provider password. If you use Azure or Google or another identity provider, XCreds will make sure the password is the same. XCreds runs in the background and checks if the cloud password has been changed. If it detects the password has changed, it prompts to log in to the cloud provider and updates the local password and the keychain password automatically.
```
% GitHub/Installomator/utils/assemble.sh xcreds DEBUG=0
2022-08-12 09:25:38 : WARN : xcreds : setting variable from argument DEBUG=0
2022-08-12 09:25:38 : REQ : xcreds : ################## Start Installomator v. 10.0beta, date 2022-08-12
2022-08-12 09:25:38 : INFO : xcreds : ################## Version: 10.0beta
2022-08-12 09:25:38 : INFO : xcreds : ################## Date: 2022-08-12
2022-08-12 09:25:38 : INFO : xcreds : ################## xcreds
2022-08-12 09:25:38 : INFO : xcreds : BLOCKING_PROCESS_ACTION=tell_user
2022-08-12 09:25:38 : INFO : xcreds : NOTIFY=success
2022-08-12 09:25:38 : INFO : xcreds : LOGGING=INFO
2022-08-12 09:25:38 : INFO : xcreds : LOGO=/System/Applications/App Store.app/Contents/Resources/AppIcon.icns
2022-08-12 09:25:38 : INFO : xcreds : Label type: pkg
2022-08-12 09:25:38 : INFO : xcreds : archiveName: XCreds.pkg
2022-08-12 09:25:38 : INFO : xcreds : no blocking processes defined, using XCreds as default
2022-08-12 09:25:38 : INFO : xcreds : No version found using packageID com.twocanoes.pkg.secureremoteaccess
2022-08-12 09:25:38 : INFO : xcreds : name: XCreds, appName: XCreds.app
2022-08-12 09:25:38 : WARN : xcreds : No previous app found
2022-08-12 09:25:38 : WARN : xcreds : could not find XCreds.app
2022-08-12 09:25:38 : INFO : xcreds : appversion:
2022-08-12 09:25:38 : INFO : xcreds : Latest version of XCreds is 1.0.0
2022-08-12 09:25:38 : REQ : xcreds : Downloading https://github.com/twocanoes/xcreds/releases/download/v1.0.0/XCreds_1_0_0_Build-1272_Version.pkg to XCreds.pkg
2022-08-12 09:25:39 : REQ : xcreds : no more blocking processes, continue with update
2022-08-12 09:25:39 : REQ : xcreds : Installing XCreds
2022-08-12 09:25:39 : INFO : xcreds : Verifying: XCreds.pkg
2022-08-12 09:25:39 : INFO : xcreds : Team ID: UXP6YEHSPW (expected: UXP6YEHSPW )
2022-08-12 09:25:39 : INFO : xcreds : Installing XCreds.pkg to /
2022-08-12 09:25:42 : INFO : xcreds : Finishing...
2022-08-12 09:25:52 : INFO : xcreds : found packageID com.twocanoes.pkg.secureremoteaccess installed, version 1.2
2022-08-12 09:25:52 : REQ : xcreds : Installed XCreds, version 1.2
2022-08-12 09:25:52 : INFO : xcreds : notifying
2022-08-12 09:25:52 : INFO : xcreds : App not closed, so no reopen.
2022-08-12 09:25:52 : REQ : xcreds : All done!
2022-08-12 09:25:52 : REQ : xcreds : ################## End Installomator, exit code 0
```
λ sudo utils/assemble.sh kap DEBUG=0
Password:
2022-06-06 14:40:02 : WARN : kap : setting variable from argument DEBUG=0
2022-06-06 14:40:02 : REQ : kap : ################## Start Installomator v. 10.0beta, date 2022-06-06
2022-06-06 14:40:02 : INFO : kap : ################## Version: 10.0beta
2022-06-06 14:40:02 : INFO : kap : ################## Date: 2022-06-06
2022-06-06 14:40:02 : INFO : kap : ################## kap
2022-06-06 14:40:03 : INFO : kap : BLOCKING_PROCESS_ACTION=tell_user
2022-06-06 14:40:03 : INFO : kap : NOTIFY=success
2022-06-06 14:40:03 : INFO : kap : LOGGING=INFO
2022-06-06 14:40:03 : INFO : kap : LOGO=/System/Applications/App Store.app/Contents/Resources/AppIcon.icns
2022-06-06 14:40:03 : INFO : kap : Label type: dmg
2022-06-06 14:40:03 : INFO : kap : archiveName: Kap-[0-9.]*-x64.dmg
2022-06-06 14:40:03 : INFO : kap : no blocking processes defined, using Kap as default
2022-06-06 14:40:03 : INFO : kap : App(s) found: /Applications/Kap.app
2022-06-06 14:40:03 : INFO : kap : found app at /Applications/Kap.app, version 3.5.3, on versionKey CFBundleShortVersionString
2022-06-06 14:40:03 : INFO : kap : appversion: 3.5.3
2022-06-06 14:40:03 : INFO : kap : Latest version of Kap is 3.5.4
2022-06-06 14:40:03 : REQ : kap : Downloading https://github.com/wulkano/Kap/releases/download/v3.5.4/Kap-3.5.4-x64.dmg to Kap-[0-9.]*-x64.dmg
2022-06-06 14:40:08 : REQ : kap : no more blocking processes, continue with update
2022-06-06 14:40:08 : REQ : kap : Installing Kap
2022-06-06 14:40:08 : INFO : kap : Mounting /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/tmp.RoYqmJzY/Kap-[0-9.]*-x64.dmg
2022-06-06 14:40:13 : INFO : kap : Mounted: /Volumes/Kap 3.5.4
2022-06-06 14:40:13 : INFO : kap : Verifying: /Volumes/Kap 3.5.4/Kap.app
2022-06-06 14:40:17 : INFO : kap : Team ID matching: 2KEEHXF6R6 (expected: 2KEEHXF6R6 )
2022-06-06 14:40:17 : INFO : kap : Downloaded version of Kap is 3.5.4 on versionKey CFBundleShortVersionString (replacing version 3.5.3).
2022-06-06 14:40:17 : INFO : kap : App has LSMinimumSystemVersion: 10.12.0
2022-06-06 14:40:17 : WARN : kap : Removing existing /Applications/Kap.app
2022-06-06 14:40:17 : INFO : kap : Copy /Volumes/Kap 3.5.4/Kap.app to /Applications
2022-06-06 14:40:18 : WARN : kap : Changing owner to lance.stephens
2022-06-06 14:40:18 : INFO : kap : Finishing...
2022-06-06 14:40:28 : INFO : kap : App(s) found: /Applications/Kap.app
2022-06-06 14:40:28 : INFO : kap : found app at /Applications/Kap.app, version 3.5.4, on versionKey CFBundleShortVersionString
2022-06-06 14:40:28 : REQ : kap : Installed Kap, version 3.5.4
2022-06-06 14:40:28 : INFO : kap : notifying
2022-06-06 14:40:29 : INFO : kap : App not closed, so no reopen.
2022-06-06 14:40:29 : REQ : kap : All done!
2022-06-06 14:40:29 : REQ : kap : ################## End Installomator, exit code 0
Now pointed to Installomator/Installomator instead of scriptingosx/Installomator
Fixes Release and Downloads badges showing "no releases or repo found" error
2022-05-13 09:41:32 : REQ : pika : ################## Start Installomator v. 9.2beta, date 2022-05-13
2022-05-13 09:41:32 : INFO : pika : ################## Version: 9.2beta
2022-05-13 09:41:32 : INFO : pika : ################## Date: 2022-05-13
2022-05-13 09:41:32 : INFO : pika : ################## pika
2022-05-13 09:41:32 : DEBUG : pika : DEBUG mode 1 enabled.
2022-05-13 09:41:33 : INFO : pika : BLOCKING_PROCESS_ACTION=tell_user
2022-05-13 09:41:33 : INFO : pika : NOTIFY=success
2022-05-13 09:41:33 : INFO : pika : LOGGING=DEBUG
2022-05-13 09:41:33 : INFO : pika : LOGO=/System/Applications/App Store.app/Contents/Resources/AppIcon.icns
2022-05-13 09:41:33 : INFO : pika : Label type: dmg
2022-05-13 09:41:33 : INFO : pika : archiveName: Pika.dmg
2022-05-13 09:41:33 : DEBUG : pika : Changing directory to /Users/thijs/gits/Installomator/build
2022-05-13 09:41:33 : INFO : pika : No version found using packageID com.superhighfives.Pika
2022-05-13 09:41:33 : INFO : pika : App(s) found: /Applications/Pika.app
2022-05-13 09:41:33 : INFO : pika : found app at /Applications/Pika.app, version 0.0.12, on versionKey CFBundleShortVersionString
2022-05-13 09:41:33 : INFO : pika : appversion: 0.0.12
2022-05-13 09:41:33 : INFO : pika : Latest version of Pika is 0.0.12
2022-05-13 09:41:33 : WARN : pika : DEBUG mode 1 enabled, not exiting, but there is no new version of app.
2022-05-13 09:41:33 : INFO : pika : Pika.dmg exists and DEBUG mode 1 enabled, skipping download
2022-05-13 09:41:33 : REQ : pika : Installing Pika
2022-05-13 09:41:33 : INFO : pika : Mounting /Users/thijs/gits/Installomator/build/Pika.dmg
2022-05-13 09:41:33 : DEBUG : pika : Debugging enabled, dmgmount output was:
expected CRC32 $02D39DFE
/dev/disk2 GUID_partition_scheme
/dev/disk2s1 Apple_HFS /Volumes/Pika
2022-05-13 09:41:34 : INFO : pika : Mounted: /Volumes/Pika
2022-05-13 09:41:34 : INFO : pika : Verifying: /Volumes/Pika/Pika.app
2022-05-13 09:41:34 : DEBUG : pika : App size: 8.0M /Volumes/Pika/Pika.app
2022-05-13 09:41:34 : DEBUG : pika : Debugging enabled, App Verification output was:
/Volumes/Pika/Pika.app: accepted
source=Notarized Developer ID
origin=Developer ID Application: Charlie Gleason (TGHU37N6EX)
2022-05-13 09:41:34 : INFO : pika : Team ID matching: TGHU37N6EX (expected: TGHU37N6EX )
2022-05-13 09:41:34 : INFO : pika : Downloaded version of Pika is 0.0.12 on versionKey CFBundleShortVersionString, same as installed.
2022-05-13 09:41:34 : DEBUG : pika : Unmounting /Volumes/Pika
2022-05-13 09:41:34 : DEBUG : pika : Debugging enabled, Unmounting output was:
"disk2" ejected.
2022-05-13 09:41:34 : DEBUG : pika : DEBUG mode 1, not reopening anything
2022-05-13 09:41:34 : REG : pika : No new version to install
2022-05-13 09:41:34 : REQ : pika : ################## End Installomator, exit code 0
2022-05-12 20:40:36 : REQ : fontexplorer : ################## Start Installomator v. 9.2beta, date 2022-05-12
2022-05-12 20:40:36 : INFO : fontexplorer : ################## Version: 9.2beta
2022-05-12 20:40:36 : INFO : fontexplorer : ################## Date: 2022-05-12
2022-05-12 20:40:36 : INFO : fontexplorer : ################## fontexplorer
2022-05-12 20:40:36 : DEBUG : fontexplorer : DEBUG mode 1 enabled.
2022-05-12 20:40:36 : INFO : fontexplorer : BLOCKING_PROCESS_ACTION=tell_user
2022-05-12 20:40:36 : INFO : fontexplorer : NOTIFY=success
2022-05-12 20:40:36 : INFO : fontexplorer : LOGGING=DEBUG
2022-05-12 20:40:36 : INFO : fontexplorer : LOGO=/System/Applications/App Store.app/Contents/Resources/AppIcon.icns
2022-05-12 20:40:37 : INFO : fontexplorer : Label type: dmg
2022-05-12 20:40:37 : INFO : fontexplorer : archiveName: FontExplorer X Pro.dmg
2022-05-12 20:40:37 : INFO : fontexplorer : no blocking processes defined, using FontExplorer X Pro as default
2022-05-12 20:40:37 : DEBUG : fontexplorer : Changing directory to /Users/thijs/gits/Installomator/build
2022-05-12 20:40:37 : INFO : fontexplorer : No version found using packageID com.linotype.FontExplorerX
2022-05-12 20:40:37 : INFO : fontexplorer : App(s) found: /Applications/FontExplorer X Pro.app
2022-05-12 20:40:37 : INFO : fontexplorer : found app at /Applications/FontExplorer X Pro.app, version 7.3.0, on versionKey CFBundleShortVersionString
2022-05-12 20:40:37 : INFO : fontexplorer : appversion: 7.3.0
2022-05-12 20:40:37 : INFO : fontexplorer : Latest version of FontExplorer X Pro is 7.3.0
2022-05-12 20:40:37 : WARN : fontexplorer : DEBUG mode 1 enabled, not exiting, but there is no new version of app.
2022-05-12 20:40:37 : REQ : fontexplorer : Downloading http://www.fontexplorerx.com/download/free-trial/Mac/ to FontExplorer X Pro.dmg
2022-05-12 20:40:58 : DEBUG : fontexplorer : File list: -rw-r--r-- 1 root staff 219M May 12 20:40 FontExplorer X Pro.dmg
2022-05-12 20:40:58 : DEBUG : fontexplorer : File type: FontExplorer X Pro.dmg: bzip2 compressed data, block size = 100k
2022-05-12 20:40:58 : DEBUG : fontexplorer : curl output was:
* Trying 104.18.180.24:80...
* Connected to www.fontexplorerx.com (104.18.180.24) port 80 (#0)
> GET /download/free-trial/Mac/ HTTP/1.1
> Host: www.fontexplorerx.com
> User-Agent: curl/7.79.1
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 301 Moved Permanently
< Date: Thu, 12 May 2022 18:40:37 GMT
< Transfer-Encoding: chunked
< Connection: keep-alive
< Cache-Control: max-age=3600
< Expires: Thu, 12 May 2022 19:40:37 GMT
< Location: https://www.fontexplorerx.com/download/free-trial/Mac/
< Set-Cookie: __cf_bm=kZPes1jyXmAENecQ_jHVQct9Dvv_ISHMkgRcS4glo0I-1652380837-0-AQPVHegSUW/AmyCHfCgPmZVwgpJlX+4Jhdd51CRneVeNlhg4cWjwzSZp1L+1T+G40HCB/aPfP1oHNCNBbcRLTS6YT7jub4dfXfD26HdNm7S8; path=/; expires=Thu, 12-May-22 19:10:37 GMT; domain=.fontexplorerx.com; HttpOnly; SameSite=None
< Server: cloudflare
< CF-RAY: 70a548a99c75972d-AMS
<
* Ignoring the response-body
{ [5 bytes data]
* Connection #0 to host www.fontexplorerx.com left intact
* Issue another request to this URL: 'https://www.fontexplorerx.com/download/free-trial/Mac/'
* Trying 104.18.180.24:443...
* Connected to www.fontexplorerx.com (104.18.180.24) port 443 (#1)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /etc/ssl/cert.pem
* CApath: none
* (304) (OUT), TLS handshake, Client hello (1):
} [326 bytes data]
* (304) (IN), TLS handshake, Server hello (2):
{ [122 bytes data]
* (304) (IN), TLS handshake, Unknown (8):
{ [19 bytes data]
* (304) (IN), TLS handshake, Certificate (11):
{ [2992 bytes data]
* (304) (IN), TLS handshake, CERT verify (15):
{ [264 bytes data]
* (304) (IN), TLS handshake, Finished (20):
{ [52 bytes data]
* (304) (OUT), TLS handshake, Finished (20):
} [52 bytes data]
* SSL connection using TLSv1.3 / AEAD-AES256-GCM-SHA384
* ALPN, server accepted to use h2
* Server certificate:
* subject: C=US; ST=Massachusetts; L=Woburn; O=Monotype Imaging Inc.; CN=*.fontexplorerx.com
* start date: Oct 7 00:00:00 2021 GMT
* expire date: Nov 7 23:59:59 2022 GMT
* subjectAltName: host "www.fontexplorerx.com" matched cert's "*.fontexplorerx.com"
* issuer: C=US; O=DigiCert Inc; CN=DigiCert TLS RSA SHA256 2020 CA1
* SSL certificate verify ok.
* Using HTTP2, server supports multiplexing
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x7fc1df00d200)
> GET /download/free-trial/Mac/ HTTP/2
> Host: www.fontexplorerx.com
> user-agent: curl/7.79.1
> accept: */*
>
* Connection state changed (MAX_CONCURRENT_STREAMS == 256)!
< HTTP/2 302
< date: Thu, 12 May 2022 18:40:37 GMT
< content-type: text/html; charset=utf-8
< location: https://fex.linotype.com/download/mac/FontExplorerXPro.dmg
< cache-control: no-cache, no-store, must-revalidate
< pragma: no-cache
< expires: -1
< x-content-type-options: nosniff
< content-security-policy: frame-ancestors 'none'
< strict-transport-security: max-age=31536002
< cf-cache-status: DYNAMIC
< expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
< set-cookie: __cf_bm=dYYK6Y7iXYOgbnA4M2wcaGi_3TSiOjfbcxSSw3Zbino-1652380837-0-AVfDaWLwFR6cAPkneaotOxDc7uxHiUEPuV92v30LSBVarfBz2BmbAgyBtIlmQBVorqV7i4ihmfqfHx+toFnCJJTxa6tymS6p9Cg6cp6Gs6hU; path=/; expires=Thu, 12-May-22 19:10:37 GMT; domain=.fontexplorerx.com; HttpOnly; Secure; SameSite=None
< server: cloudflare
< cf-ray: 70a548aa1d8e0b43-AMS
<
* Ignoring the response-body
{ [175 bytes data]
* Connection #1 to host www.fontexplorerx.com left intact
* Issue another request to this URL: 'https://fex.linotype.com/download/mac/FontExplorerXPro.dmg'
* Trying 104.16.65.114:443...
* Connected to fex.linotype.com (104.16.65.114) port 443 (#2)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /etc/ssl/cert.pem
* CApath: none
* (304) (OUT), TLS handshake, Client hello (1):
} [321 bytes data]
* (304) (IN), TLS handshake, Server hello (2):
{ [122 bytes data]
* (304) (IN), TLS handshake, Unknown (8):
{ [19 bytes data]
* (304) (IN), TLS handshake, Certificate (11):
{ [2979 bytes data]
* (304) (IN), TLS handshake, CERT verify (15):
{ [264 bytes data]
* (304) (IN), TLS handshake, Finished (20):
{ [52 bytes data]
* (304) (OUT), TLS handshake, Finished (20):
} [52 bytes data]
* SSL connection using TLSv1.3 / AEAD-AES256-GCM-SHA384
* ALPN, server accepted to use h2
* Server certificate:
* subject: C=US; ST=Massachusetts; L=Woburn; O=Monotype Imaging Inc.; CN=*.linotype.com
* start date: Oct 19 00:00:00 2021 GMT
* expire date: Nov 19 23:59:59 2022 GMT
* subjectAltName: host "fex.linotype.com" matched cert's "*.linotype.com"
* issuer: C=US; O=DigiCert Inc; CN=DigiCert TLS RSA SHA256 2020 CA1
* SSL certificate verify ok.
* Using HTTP2, server supports multiplexing
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x7fc1df00d200)
> GET /download/mac/FontExplorerXPro.dmg HTTP/2
> Host: fex.linotype.com
> user-agent: curl/7.79.1
> accept: */*
>
* Connection state changed (MAX_CONCURRENT_STREAMS == 256)!
< HTTP/2 301
< date: Thu, 12 May 2022 18:40:37 GMT
< content-type: text/html; charset=iso-8859-1
< location: https://fex.linotype.com/download/mac/FontExplorerXPro730.dmg
< x-content-type-options: nosniff
< strict-transport-security: max-age=600
< cf-cache-status: HIT
< age: 434
< expires: Thu, 12 May 2022 22:40:37 GMT
< cache-control: public, max-age=14400
< expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
< set-cookie: __cf_bm=SlfrZLCGpjb6KyGZO8AA0rwgarMWV7kPmFXBLTzy5W4-1652380837-0-AbVvJxFnFOqL80rmdoW6+BJoGPtsSkZracJNOqpaUuwfkPqWxPXamLI3d94NaQ7loSyoYWq7sQEi2MBI2EVzhlg=; path=/; expires=Thu, 12-May-22 19:10:37 GMT; domain=.linotype.com; HttpOnly; Secure; SameSite=None
< server: cloudflare
< cf-ray: 70a548acfe324c61-AMS
<
* Ignoring the response-body
{ [269 bytes data]
* Connection #2 to host fex.linotype.com left intact
* Issue another request to this URL: 'https://fex.linotype.com/download/mac/FontExplorerXPro730.dmg'
* Found bundle for host fex.linotype.com: 0x600000236f70 [can multiplex]
* Re-using existing connection! (#2) with host fex.linotype.com
* Connected to fex.linotype.com (104.16.65.114) port 443 (#2)
* Using Stream ID: 3 (easy handle 0x7fc1df00d200)
> GET /download/mac/FontExplorerXPro730.dmg HTTP/2
> Host: fex.linotype.com
> user-agent: curl/7.79.1
> accept: */*
>
< HTTP/2 301
< date: Thu, 12 May 2022 18:40:37 GMT
< content-type: text/html; charset=iso-8859-1
< location: https://fast.fontexplorerx.com/FontExplorerXPro730.dmg
< x-content-type-options: nosniff
< strict-transport-security: max-age=600
< cf-cache-status: HIT
< age: 433
< expires: Thu, 12 May 2022 22:40:37 GMT
< cache-control: public, max-age=14400
< expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
< set-cookie: __cf_bm=Q4TbFu6Pl0l_HkUJCmCaf5rQaPllv5YED.XM2SL79U8-1652380837-0-AW4DU7pcHEiy+fHl61+ok4XgWh0nEcH+xQmqFXKJiv7H+3qCrGMgF3VX72WPtXrPszVJXl5V0uRNL2er8uChQpk=; path=/; expires=Thu, 12-May-22 19:10:37 GMT; domain=.linotype.com; HttpOnly; Secure; SameSite=None
< server: cloudflare
< cf-ray: 70a548ad2e6d4c61-AMS
<
* Ignoring the response-body
{ [262 bytes data]
* Connection #2 to host fex.linotype.com left intact
* Issue another request to this URL: 'https://fast.fontexplorerx.com/FontExplorerXPro730.dmg'
* Trying 104.18.181.24:443...
* Connected to fast.fontexplorerx.com (104.18.181.24) port 443 (#3)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /etc/ssl/cert.pem
* CApath: none
* (304) (OUT), TLS handshake, Client hello (1):
} [327 bytes data]
* (304) (IN), TLS handshake, Server hello (2):
{ [122 bytes data]
* (304) (IN), TLS handshake, Unknown (8):
{ [19 bytes data]
* (304) (IN), TLS handshake, Certificate (11):
{ [2992 bytes data]
* (304) (IN), TLS handshake, CERT verify (15):
{ [264 bytes data]
* (304) (IN), TLS handshake, Finished (20):
{ [52 bytes data]
* (304) (OUT), TLS handshake, Finished (20):
} [52 bytes data]
* SSL connection using TLSv1.3 / AEAD-AES256-GCM-SHA384
* ALPN, server accepted to use h2
* Server certificate:
* subject: C=US; ST=Massachusetts; L=Woburn; O=Monotype Imaging Inc.; CN=*.fontexplorerx.com
* start date: Oct 7 00:00:00 2021 GMT
* expire date: Nov 7 23:59:59 2022 GMT
* subjectAltName: host "fast.fontexplorerx.com" matched cert's "*.fontexplorerx.com"
* issuer: C=US; O=DigiCert Inc; CN=DigiCert TLS RSA SHA256 2020 CA1
* SSL certificate verify ok.
* Using HTTP2, server supports multiplexing
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x7fc1df00d200)
> GET /FontExplorerXPro730.dmg HTTP/2
> Host: fast.fontexplorerx.com
> user-agent: curl/7.79.1
> accept: */*
>
* Connection state changed (MAX_CONCURRENT_STREAMS == 256)!
< HTTP/2 200
< date: Thu, 12 May 2022 18:40:38 GMT
< content-type: application/x-apple-diskimage
< content-length: 229482072
< x-amz-id-2: rrcC6JFnkN2jtYk94tMm+523tEdrKttw5CAFgpRxGam9Q+CbHoM/Uh574h1Tiej44o+/Y/NwdLY=
< x-amz-request-id: CB8VSYEZ9B03GME4
< last-modified: Wed, 02 Mar 2022 10:13:51 GMT
< etag: "1e88553987c85a58640ed89b09b3905a-14"
< x-amz-version-id: cnP65ReMq6hht_tJxn6vOaTLvOrEPBC8
< cf-cache-status: HIT
< age: 434
< expires: Thu, 12 May 2022 22:40:38 GMT
< cache-control: public, max-age=14400
< accept-ranges: bytes
< expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
< set-cookie: __cf_bm=fXzImTkInEiKHLNXQKjb4ssMB7TRhWIvw3OZqbnDGYA-1652380838-0-AVO+uwdFQxX4T6ttCaCyQ0IvfqwyaOvkySC4KiaQDqZv7Z9xZDH9qDg1jUHyTJNVdZEnTT1Z7YH3I3xRC4NWKJOHeHnD3lmDBXorIH2I7uRv; path=/; expires=Thu, 12-May-22 19:10:38 GMT; domain=.fontexplorerx.com; HttpOnly; Secure; SameSite=None
< server: cloudflare
< cf-ray: 70a548ad99424bef-AMS
<
{ [701 bytes data]
* Connection #3 to host fast.fontexplorerx.com left intact
2022-05-12 20:40:58 : DEBUG : fontexplorer : DEBUG mode 1, not checking for blocking processes
2022-05-12 20:40:58 : REQ : fontexplorer : Installing FontExplorer X Pro
2022-05-12 20:40:59 : INFO : fontexplorer : Mounting /Users/thijs/gits/Installomator/build/FontExplorer X Pro.dmg
2022-05-12 20:41:20 : DEBUG : fontexplorer : Debugging enabled, dmgmount output was:
FontExplorer X Software License Agreement We recommend that you
print this Agreement for further reference. This FontExplorer X
Software License Agreement (this “Agreement”) becomes a binding
contract between you and Monotype, when you click on the area marked
“ACCEPT LICENSE AGREEMENT” (or such similar language). If you do
not wish to be bound by this Agreement, you may not Use the
FontExplorer X Software. Please read all of this Agreement before
you agree to be bound by its terms and conditions. 1. Definitions
Defined terms used throughout this Agreement: “Critical Patch
Releases” means updates to the FontExplorer X Software that Monotype
determines, in its sole discretion, will be made available on a
general basis to all of its customers. Critical Patch Releases may
or may not include certain changes that are included in an Update
and may be released before or after any such Update is provided to
eligible customers. A Critical Patch Release may, in Monotype’s
sole discretion, be released prior to completion of Monotype’s
complete quality assurance testing process. “Device” means any
piece of electronic equipment or mechanism designed to serve a
special purpose or perform a special function, including, but not
limited to, a desktop computer, server or laptop. “FontExplorer X
Pro Software” means all the contents of the files, CD-ROM, DVD-ROM
or other media relating to Monotype’s proprietary FontExplorer X
Pro Software product if such product is provided to you under this
Agreement. The FontExplorer X Pro Software may include Plugins
delivered as part of the FontExplorer X Pro Software package,
Updates, Upgrades, Critical Patch Releases, permitted copies, and
related documentation, in each case which may be provided to you
by Monotype in its sole discretion. “FontExplorer X Server Software”
means all the contents of the files, CD-ROM, DVD-ROM or other media
relating to Monotype’s proprietary FontExplorer X Server Software
product if such product is provided to you under this Agreement.
The FontExplorer X Server Software may include Updates, Upgrades,
Critical Patch Releases, permitted copies, and related documentation,
in each case which may be provided to you by Monotype in its sole
discretion. “FontExplorer X Software” means the FontExplorer X Pro
Software or the FontExplorer X Thin Client Software and, as the
case may be, the FontExplorer X Server Software. “FontExplorer X
Thin Client Software” means the all contents of the files, CD-ROM,
DVD-ROM or other media relating to Monotype’s proprietary FontExplorer
X Thin Client Software product if such product is provided to you
under this Agreement. The FontExplorer X Thin Client Software may
include Plugins delivered as part of the FontExplorer X Thin Client
Software package, Updates, Upgrades, Critical Patch Releases,
permitted copies, and related documentation, in each case which may
be provided to you by Monotype in its sole discretion. “Licensed
Server” means a Device that the FontExplorer X Server Software runs
on, regardless of other purposes the Device may be used for, and
which shall remain in your sole care, custody and control (or, if
the Licensed Server is hosted by an internet service provider for
your benefit, you shall be responsible for all content on the
Licensed Server, as well as access to and security for such content).
“Licensed User” means you and, so long as they have been notified
by you of the terms and conditions of this Agreement and have agreed
to be bound by it, (i) if you are an individual, members of your
immediate household or (ii) if you are a business entity, your
employees and any contractors, in each case subject to the limit
of the number of users specified in the respective invoice(s) or
licensing document(s). “Monotype” means collectively Monotype
Imaging Inc., 600 Unicorn Park Drive, Woburn, Massachusetts 01801,
USA, its successors and assigns, its parent and affiliated corporations,
its authorized distributors, and any third party which has licensed
to Monotype any or all of the components of the FontExplorer X
Software supplied to you pursuant to this Agreement. “Software
Releases” are newly named products which provide unique functionality
beyond the scope of previously released software products and which
will be made available to customers for an additional fee. “Trial
Period” is a period defined by the communication between you and
Monotype to evaluate FontExplorer X Software in accordance with the
terms of this Agreement. “Update” means any bug fixes or minor
debugging that revises or corrects inefficiencies or defects in the
FontExplorer X Software. Some specific updates may include a Critical
Patch Release in Monotype’s sole discretion. Updates shall not
include any Upgrades or Software Releases. “Upgrade” means a new
version of the FontExplorer X Software which provides product
updates, feature enhancements and/or the foundation for additional
functionality beyond that contained in the most recent version of
the FontExplorer X Software. Upgrades shall not include any Software
Releases. “Use” of the FontExplorer X Software shall occur when
it is downloaded, installed, executed, accessed or an individual
or entity otherwise benefits from the FontExplorer X Software. 2.
Scope
You are bound by this Agreement and you acknowledge that
all Use of the FontExplorer X Software is governed by this
Agreement. You are responsible for any breach of this
Agreement by a Licensed User.
3. License Grants 3.1 FontExplorer X Server Software. If
the quotation appertaining to this Agreement references the
FontExplorer X Server Software you are hereby granted, unless you
obtain the FontExplorer X Server Software for a Trial Period, subject
to the payment of the applicable license fees, and subject to the
terms and conditions of this Agreement, a non-exclusive, non-assignable,
non-transferable (if the FontExplorer X Software was not acquired
through a subscription except as expressly permitted in Section 9
of this Agreement) license to (i) Use the FontExplorer X Server
Software on Licensed Servers and (ii) to permit Licensed Users to
access and Use the FontExplorer X Server Software through Devices
or through an internal local area network (LAN) which includes
connections though a Virtual Private Network (VPN). 3.2
FontExplorer X Pro Software or FontExplorer X Thin Client Software.
Subject to the payment of the applicable license fees, and subject
to the terms and conditions of this Agreement, each Licensed User
is hereby granted a non-exclusive, non-assignable, non-transferable
(if the FontExplorer X Software or the FontExplorer X Thin Client
Software was not acquired through a subscription except as expressly
permitted in Section 9 of this Agreement) license to copy and Use
the FontExplorer X Pro Software or FontExplorer X Thin Client
Software on Devices which a Licensed User may access under the
condition that persons other than Licensed Users are excluded from
Use of the FontExplorer X Pro Software or FontExplorer X Thin Client
Software. The FontExplorer X Pro Software or FontExplorer X Thin
Client Software may be Used from a server (through a LAN or external
network system) as long as such Use is restricted to Licensed Users.
4. Copies and Modifications 4.1 FontExplorer X Server
Software. If the quotation appertaining to this Agreement references
the FontExplorer X Server Software you may make one back-up copy
of the FontExplorer X Server Software for archival purposes only,
and you shall retain exclusive custody and control over such copy.
Such copy must contain the same copyright, trademark, and other
proprietary notices that appear on or in the FontExplorer X Server
Software. 4.2 FontExplorer X Pro Software or FontExplorer X
Thin Client Software. With the exception of making copies of the
FontExplorer X Pro Software or FontExplorer X Thin Client Software
for Devices which a Licensed User may access as provided by 3.2, a
Licensed User may make one back-up copy of the FontExplorer X Pro
Software or FontExplorer X Thin Client Software for archival purposes
only, and such Licensed User shall retain exclusive custody and
control over such copy. Such copy must contain the same copyright,
trademark, and other proprietary notices that appear on or in the
FontExplorer X Pro Software or FontExplorer X Thin Client Software.
4.3 Additional Restrictions. You may not, and you will not
encourage, assist or authorize any other person to: ¥ Install
the FontExplorer X Server Software on Devices other than on a
Licensed Server; ¥ Use the FontExplorer X Software if such
person is not a Licensed User; ¥ sublicense, rent or lease,
adapt, modify, alter, translate, convert, create any derivative
work or otherwise change the FontExplorer X Software or any portion
thereof; or ¥ reverse engineer, decompile, disassemble, or
otherwise attempt to discover the source code of the FontExplorer X
Software or any portion thereof, provided, however, that if you are
located in a European Community member country or any other country
which provides rights materially similar to the rights set forth
in this proviso, you may reverse engineer or decompile the
FontExplorer X Software only to the extent that sufficient information
is not available for the purpose of creating an interoperable
software program (but only for such purpose and only to the extent
that sufficient information is not provided by Monotype upon written
request). You agree not to publish, or make otherwise accessible
to the public, the information arrived at through reverse engineering
and/or decompiling for the purpose of achieving interoperability.
4.4 Ownership. If you modify or create a derivative work of the
FontExplorer X Software, Monotype becomes the owner of the modified
data and/or derivative work. 5. Purchases of Font Software
through the FontExplorer X Pro Software 5.1 In order to purchase
font software products through the FontExplorer X Pro Software, a
Licensed User must register with Monotype. You agree to provide
accurate, current, and complete information and to maintain and
update the registration data as required. Personal data will be
collected, processed and used only by Monotype and its affiliated
companies to provide the services specified herein. In accordance
with the principle of the efficient collection of data, Monotype
will only collect personal data that is necessary to fulfill the
contract and provide the services hereunder. 5.2 Any purchase
of font software products made through the FontExplorer X Pro
Software is subject to the respective foundries’ End User License
Agreement (EULA). The EULAs may be updated by the respective foundry
from time to time and the EULA in effect at the time a Licensed
User purchases a particular font software product shall apply to
that font software product. A breach of any such EULA will also
constitute a breach of this Agreement. 6. Licensing Information
The FontExplorer X Software may contain license information
about the fonts that are loaded in its repository (e. g.
number of licenses per font). To the extent that you or a
Licensed User enter or change such license information, you
agree that such information is and will be at all times
correct and complete.
7. Reservation of Rights 7.1 You acknowledge that the
FontExplorer X Software is protected by the copyright of the United
States of America, by the copyright laws of other nations, and by
international treaties. Neither you nor any Licensed User has rights
to the FontExplorer X Software other than as expressly set forth
in this Agreement. You agree that Monotype or its licensors owns
all right, title and interest in and to the FontExplorer X Software,
its structure, organization, code, and related files, including all
property rights therein such as copyright, design and trademarks
rights. You agree that the FontExplorer X Software, its structure,
organization, code, and related files (including, without limitation,
its metrics) are valuable property of Monotype and that any intentional
Use of the FontExplorer X Software not expressly permitted by this
Agreement constitutes a theft of valuable property. You agree to
treat the FontExplorer X Software as you would any other copyrighted
material, such as a book. All rights not expressly granted in this
Agreement are expressly reserved to Monotype. 7.2 Monotype,
the Monotype logo, FontExplorer X and other Monotype trademarks
used in connection with the FontExplorer X Software are trademarks
or registered trademarks of Monotype Imaging Inc. or Monotype GmbH
in the U.S., Germany and/or other countries. Neither you nor any
Licensed User is granted any right or license with respect to any
of the aforementioned trademarks or any use of such trademarks. You
agree to use trademarks associated with the FontExplorer X Software
according to accepted trademark practice, including identification
of the trademark owner’s name. The use of any trademark as herein
authorized does not give you any rights of ownership in that trademark
and all use of any trademark shall inure to the sole benefit of
Monotype. 8. Warranty; Disclaimer of Warranty; Liability
Limitations 8.1 Monotype warrants to you that the FontExplorer X
Software will perform in accordance with its documentation for the
ninety (90) day period following delivery. To make a warranty claim,
you must, within the ninety (90) day warranty period, notify Monotype.
8.2 MONOTYPE DOES NOT WARRANT THE PERFORMANCE OR RESULTS YOU
MAY OBTAIN BY USING THE FONTEXPLORER X SOFTWARE. TO THE GREATEST
EXTENT PERMITTED BY LAW THE FOREGOING STATES THE SOLE AND EXCLUSIVE
REMEDIES FOR MONOTYPE’S BREACH OF WARRANTY. EXCEPT FOR THE FOREGOING
LIMITED WARRANTY, MONOTYPE MAKES NO REPRESENTATIONS OR WARRANTIES,
EXPRESS OR IMPLIED, AS TO NON-INFRINGEMENT OF THIRD PARTY RIGHTS,
MERCHANTABILITY, OR FITNESS FOR ANY PARTICULAR PURPOSE. 8.3 TO
THE EXTENT PERMITTED BY THE APPLICABLE LAW MONOTYPE WILL NOT BE
LIABLE TO YOU OR ANYONE ELSE (I) FOR ANY CONSEQUENTIAL, INCIDENTAL
OR SPECIAL DAMAGES, INCLUDING WITHOUT LIMITATION ANY LOST PROFITS,
LOST DATA, LOST BUSINESS OPPORTUNITIES, OR LOST SAVINGS, EVEN IF
MONOTYPE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES, OR
(II) FOR ANY CLAIM AGAINST YOU BY ANY THIRD PARTY SEEKING SUCH
DAMAGES EVEN IF MONOTYPE HAS BEEN ADVISED OF THE POSSIBILITY OF
SUCH DAMAGES. 8.4 THE ABOVE LIMITATIONS OF LIABILITY WILL NOT
APPLY IF THE CAUSE OF THE DAMAGE WAS DELIBERATE OR DUE TO GROSS
NEGLIGENCE OR IF PERSONAL INJURY HAS OCCURRED. NEITHER WILL IT APPLY
IF YOU RAISE COMPULSORILY LEGALLY-BASED CLAIMS. 8.5 IN NO EVENT
SHALL MONOTYPE’S LIABILITY EXCEED ONE HUNDRED THOUSAND EURO (€
100,000.00), PROVIDED THAT THE APPLICABLE LAW PERMITS SUCH LIMITATION
OF LIABILITY. 8.6 To the greatest extent permitted by law, any
implied warranties not effectively excluded by this Agreement are
limited to thirty (30) days. 9. Transfers
Unless you acquire the FontExplorer X Software through a
subscription or for a Trial Period you may transfer all
your rights to Use the FontExplorer X Software to another
person or legal entity provided that (i) all such software
must be transferred simultaneously, (ii) the transferee
accepts and agrees in writing to be bound by all the terms
and conditions of this Agreement, (iii) you forward a copy
of such writing to Monotype, (iv) you destroy all copies
of the FontExplorer X Software not transferred to the
transferee, including all copies stored in the memory of a
hardware device, and (v) you cease all Use of the FontExplorer X
Software.
10. Term and Termination 10.1 If you acquire the FontExplorer
X Software through a subscription, this Agreement shall be effective
as of the date of acceptance of this Agreement and subscription to
the Monotype Web Fonts Service and will remain in effect for the
term of such subscription unless earlier terminated in accordance
with the terms hereof. If you acquire the FontExplorer X Software
for a Trial Period, the term of a Trial Period shall be from the
date of delivery of the FontExplorer X Software and shall terminate
automatically after the period defined in the communication between
you and Monotype. If no term is communicated then the Trial Period’s
term shall automatically end thirty (30) days after the delivery.
If you acquire the FontExplorer X Software by other means, this
Agreement shall be effective as of the date of acceptance of this
Agreement and will remain in effect unless terminated in accordance
with the terms hereof. 10.2 If you or any Licensed User fails
to comply with any of the provisions of this Agreement or any
Licensed User fails to comply with the terms of a EULA relating to
font software purchased through the FontExplorer X Pro Software,
Monotype, at its sole discretion, may (i) terminate this Agreement
and/or the account of any Licensed User, (ii) terminate any license
to font software purchased through the FontExplorer X Pro Software,
and/or (iii) preclude access to the service offered through the
FontExplorer X Software. The termination of this Agreement shall
not preclude Monotype from suing you for damages resulting from any
breach of this Agreement or any EULA relating to purchased font
software products. 10.3 You will remain liable for all amounts
due to Monotype up to and including the date of termination. 10.4
Upon termination of this Agreement, you must destroy the original
and any and all copies of, and cease all Use of, the FontExplorer X
Software. 11. Miscellaneous 11.1 Governing Law and Forum.
Unless you enter into this agreement through the Monotype affiliate
Monotype Ltd. or Monotype GmbH, or unless otherwise set forth in
writing in the agreement between you and Monotype, the agreement
entered into between you and Monotype is governed by the laws of
Massachusetts applicable to contracts wholly entered and performable
within such Commonwealth (without regard to applicable conflict of
laws provisions). The United States District Court for the District
of Massachusetts or, if federal subject matter jurisdiction is
lacking, the Superior Court of the Commonwealth of Massachusetts
in Middlesex County, shall be the exclusive forum for any disputes
arising out of or related to such agreement. Both you and Monotype
agree to the personal jurisdiction and venue of these courts in any
action related to such agreement.
If you enter into this agreement through the Monotype
affiliate Monotype Ltd. the agreement is governed by the
laws of England and Wales (without regard to applicable
conflict of laws provisions). The courts of London, England,
shall be the exclusive forum for any disputes arising out
of or related to such agreement. Both you and Monotype Ltd.
agree to the personal jurisdiction and venue of these courts
in any action related to such agreement. If you enter into
this agreement through the Monotype affiliate Monotype GmbH
the agreement is governed by the laws of Germany (without
regard to applicable conflict of laws provisions). The
courts of Frankfurt/Main, Germany, shall be the exclusive
forum for any disputes arising out of or related to such
agreement. Both you and Monotype GmbH agree to the personal
jurisdiction and venue of these courts in any action related
to such agreement. The agreement will not be governed by
the United Nations Convention of Contracts for the International
Sale of Goods, the application of which is expressly excluded.
11.2 Supplementary Support. If you have entered into a
separate FontExplorer X Software support agreement or into another
prior FontExplorer X Software agreement that included support, the
support may continue as specified in the support agreement or prior
FontExplorer X Software agreement, notwithstanding any change of
the terms of this Agreement. The continued support may require a
renewal of the respective agreement. 11.3 Entire Agreement.
This Agreement, together with any agreement “clicked through” by
you in connection with the installation of the FontExplorer X Pro
Software or FontExplorer X Thin Client Software, constitutes the
entire agreement between you and Monotype that governs the use of
the FontExplorer X Software, superseding any prior agreements between
you and Monotype. Each party owes to the other party a duty to
co-operate in order to give full effect to this Agreement. 11.4
Severability. If any part of this Agreement is held invalid or
unenforceable, that portion shall be construed in a manner consistent
with applicable law to reflect, as nearly as possible, the original
intention of the parties, and the remaining portions shall remain
in full force and effect. 11.5 No Waiver. Monotype’s failure
to enforce any right or provisions in this Agreement will not
constitute a waiver of such provision, or any other provision of
this Agreement. 11.6 Government End Users. If this product is
acquired under the terms of a (i) GSA contract - use, reproduction
or disclosure is subject to the restrictions set forth in the
applicable ADP Schedule contract, (ii) DOD contract - use, duplication
or disclosure by the Government is subject to the applicable
restrictions set forth in DFARS 252.277-7013; (iii) Civilian agency
contract - use, reproduction, or disclosure is subject to FAR
52.277-19(a) through (d) and restrictions set forth in the Agreement.
FontExplorer X Software License Agreement clickthrough (v160909)
Checksumming Driver Descriptor Map (DDM : 0)…
Driver Descriptor Map (DDM : 0): verified CRC32 $DA8F7176
Checksumming Apple (Apple_partition_map : 1)…
Apple (Apple_partition_map : 1): verified CRC32 $73B16945
Checksumming disk image (Apple_HFS : 2)…
disk image (Apple_HFS : 2): verified CRC32 $256DD0EC
Checksumming (Apple_Free : 3)…
(Apple_Free : 3): verified CRC32 $00000000
verified CRC32 $2B19FAF6
/dev/disk2 Apple_partition_scheme
/dev/disk2s1 Apple_partition_map
/dev/disk2s2 Apple_HFS /Volumes/FontExplorer X Pro
2022-05-12 20:41:20 : INFO : fontexplorer : Mounted: /Volumes/FontExplorer X Pro
2022-05-12 20:41:20 : INFO : fontexplorer : Verifying: /Volumes/FontExplorer X Pro/FontExplorer X Pro.app
2022-05-12 20:41:20 : DEBUG : fontexplorer : App size: 353M /Volumes/FontExplorer X Pro/FontExplorer X Pro.app
2022-05-12 20:42:04 : DEBUG : fontexplorer : Debugging enabled, App Verification output was:
/Volumes/FontExplorer X Pro/FontExplorer X Pro.app: accepted
source=Notarized Developer ID
origin=Developer ID Application: Linotype GmbH (2V7G2B7WG4)
2022-05-12 20:42:04 : INFO : fontexplorer : Team ID matching: 2V7G2B7WG4 (expected: 2V7G2B7WG4 )
2022-05-12 20:42:04 : INFO : fontexplorer : Downloaded version of FontExplorer X Pro is 7.3.0 on versionKey CFBundleShortVersionString, same as installed.
2022-05-12 20:42:04 : DEBUG : fontexplorer : Unmounting /Volumes/FontExplorer X Pro
2022-05-12 20:42:15 : DEBUG : fontexplorer : Debugging enabled, Unmounting output was:
"disk2" ejected.
2022-05-12 20:42:15 : DEBUG : fontexplorer : DEBUG mode 1, not reopening anything
2022-05-12 20:42:15 : REG : fontexplorer : No new version to install
2022-05-12 20:42:15 : REQ : fontexplorer : ################## End Installomator, exit code 0
the exact same as the bluejeans label, but with a new variable choiceChangesXML
this allows the package to be customized on installation which in this instance will have the BlueJeans Audio Driver installed with the software.
BlueJeans Events by Verizon only has one install package available currently, does not have architecture specific URLs.
Added install logic for "bluejeansevents" starting on line 1720
Trying to determine the language of the user, and then installing that localized version, instead of en_US. But it will fall back to en_US if something goes wrong.
```
Installomator/utils/assemble.sh houdahtembo DEBUG=0 INSTALL=force
2022-02-25 11:27:28 : REQ : houdahtembo : setting variable from argument DEBUG=0
2022-02-25 11:27:28 : REQ : houdahtembo : setting variable from argument INSTALL=force
2022-02-25 11:27:28 : REQ : houdahtembo : ################## Start Installomator v. 9.1beta, date 2022-02-25
2022-02-25 11:27:28 : INFO : houdahtembo : ################## Version: 9.1beta
2022-02-25 11:27:28 : INFO : houdahtembo : ################## Date: 2022-02-25
2022-02-25 11:27:28 : INFO : houdahtembo : ################## houdahtembo
2022-02-25 11:27:30 : INFO : houdahtembo : BLOCKING_PROCESS_ACTION=tell_user
2022-02-25 11:27:30 : INFO : houdahtembo : NOTIFY=success
2022-02-25 11:27:30 : INFO : houdahtembo : LOGGING=INFO
2022-02-25 11:27:30 : INFO : houdahtembo : LOGO=/System/Applications/App Store.app/Contents/Resources/AppIcon.icns
2022-02-25 11:27:30 : INFO : houdahtembo : Label type: zip
2022-02-25 11:27:30 : INFO : houdahtembo : archiveName: Tembo.zip
2022-02-25 11:27:30 : INFO : houdahtembo : no blocking processes defined, using Tembo as default
2022-02-25 11:27:30 : INFO : houdahtembo : App(s) found: /Applications/Tembo.app
2022-02-25 11:27:30 : INFO : houdahtembo : found app at /Applications/Tembo.app, version 2.6, on versionKey CFBundleShortVersionString
2022-02-25 11:27:30 : INFO : houdahtembo : appversion: 2.6
2022-02-25 11:27:30 : INFO : houdahtembo : Label is not of type “updateronly”, and it’s set to use force to install or ignoring app store apps, so not using updateTool.
2022-02-25 11:27:30 : INFO : houdahtembo : Latest version of Tembo is 2.6
2022-02-25 11:27:30 : INFO : houdahtembo : There is no newer version available.
2022-02-25 11:27:30 : REQ : houdahtembo : Downloading https://dl.houdah.com/tembo/updates/cast2_assets/Tembo2.6.zip to Tembo.zip
2022-02-25 11:27:35 : REQ : houdahtembo : no more blocking processes, continue with update
2022-02-25 11:27:35 : REQ : houdahtembo : Installing Tembo
2022-02-25 11:27:35 : INFO : houdahtembo : Unzipping Tembo.zip
2022-02-25 11:27:35 : INFO : houdahtembo : Verifying: /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/tmp.RzdJx8SQ/Tembo.app
2022-02-25 11:27:35 : INFO : houdahtembo : Team ID matching: DKGQD8H8ZY (expected: DKGQD8H8ZY )
2022-02-25 11:27:35 : INFO : houdahtembo : Downloaded version of Tembo is 2.6 on versionKey CFBundleShortVersionString, same as installed.
2022-02-25 11:27:35 : INFO : houdahtembo : Using force to install anyway.
2022-02-25 11:27:35 : INFO : houdahtembo : App has LSMinimumSystemVersion: 10.11
2022-02-25 11:27:36 : INFO : houdahtembo : Copy /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/tmp.RzdJx8SQ/Tembo.app to /Applications
2022-02-25 11:27:36 : INFO : houdahtembo : Changing owner to st
2022-02-25 11:27:36 : INFO : houdahtembo : Finishing...
2022-02-25 11:27:46 : INFO : houdahtembo : App(s) found: /Applications/Tembo.app
2022-02-25 11:27:46 : INFO : houdahtembo : found app at /Applications/Tembo.app, version 2.6, on versionKey CFBundleShortVersionString
2022-02-25 11:27:46 : INFO : houdahtembo : Installed Tembo, version 2.6
2022-02-25 11:27:46 : INFO : houdahtembo : notifying
2022-02-25 11:27:46 : INFO : houdahtembo : App not closed, so no reopen.
2022-02-25 11:27:46 : INFO : houdahtembo :
2022-02-25 11:27:46 : REQ : houdahtembo : ################## End Installomator, exit code 0
```
```
Installomator/utils/assemble.sh houdahspot DEBUG=0 INSTALL=force
2022-02-25 09:22:23 : REQ : houdahspot : setting variable from argument DEBUG=0
2022-02-25 09:22:23 : REQ : houdahspot : setting variable from argument INSTALL=force
2022-02-25 09:22:23 : REQ : houdahspot : ################## Start Installomator v. 9.1beta, date 2022-02-25
2022-02-25 09:22:23 : INFO : houdahspot : ################## Version: 9.1beta
2022-02-25 09:22:23 : INFO : houdahspot : ################## Date: 2022-02-25
2022-02-25 09:22:23 : INFO : houdahspot : ################## houdahspot
2022-02-25 09:22:25 : INFO : houdahspot : BLOCKING_PROCESS_ACTION=tell_user
2022-02-25 09:22:25 : INFO : houdahspot : NOTIFY=success
2022-02-25 09:22:25 : INFO : houdahspot : LOGGING=INFO
2022-02-25 09:22:25 : INFO : houdahspot : LOGO=/System/Applications/App Store.app/Contents/Resources/AppIcon.icns
2022-02-25 09:22:25 : INFO : houdahspot : Label type: zip
2022-02-25 09:22:25 : INFO : houdahspot : archiveName: HoudahSpot.zip
2022-02-25 09:22:25 : INFO : houdahspot : no blocking processes defined, using HoudahSpot as default
2022-02-25 09:22:25 : INFO : houdahspot : App(s) found: /Applications/HoudahSpot.app
2022-02-25 09:22:25 : INFO : houdahspot : found app at /Applications/HoudahSpot.app, version 6.1.11, on versionKey CFBundleShortVersionString
2022-02-25 09:22:25 : INFO : houdahspot : appversion: 6.1.11
2022-02-25 09:22:25 : INFO : houdahspot : Label is not of type “updateronly”, and it’s set to use force to install or ignoring app store apps, so not using updateTool.
2022-02-25 09:22:25 : INFO : houdahspot : Latest version of HoudahSpot is 6.1.11
2022-02-25 09:22:25 : INFO : houdahspot : There is no newer version available.
2022-02-25 09:22:25 : REQ : houdahspot : Downloading https://dl.houdah.com/houdahSpot/updates/cast6_assets/HoudahSpot6.1.11.zip to HoudahSpot.zip
2022-02-25 09:22:32 : REQ : houdahspot : no more blocking processes, continue with update
2022-02-25 09:22:32 : REQ : houdahspot : Installing HoudahSpot
2022-02-25 09:22:32 : INFO : houdahspot : Unzipping HoudahSpot.zip
2022-02-25 09:22:32 : INFO : houdahspot : Verifying: /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/tmp.O8lA89oA/HoudahSpot.app
2022-02-25 09:22:33 : INFO : houdahspot : Team ID matching: DKGQD8H8ZY (expected: DKGQD8H8ZY )
2022-02-25 09:22:33 : INFO : houdahspot : Downloaded version of HoudahSpot is 6.1.11 on versionKey CFBundleShortVersionString, same as installed.
2022-02-25 09:22:33 : INFO : houdahspot : Using force to install anyway.
2022-02-25 09:22:33 : INFO : houdahspot : App has LSMinimumSystemVersion: 10.14
2022-02-25 09:22:33 : INFO : houdahspot : Copy /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/tmp.O8lA89oA/HoudahSpot.app to /Applications
2022-02-25 09:22:33 : INFO : houdahspot : Changing owner to st
2022-02-25 09:22:33 : INFO : houdahspot : Finishing...
2022-02-25 09:22:43 : INFO : houdahspot : App(s) found: /Applications/HoudahSpot.app
2022-02-25 09:22:43 : INFO : houdahspot : found app at /Applications/HoudahSpot.app, version 6.1.11, on versionKey CFBundleShortVersionString
2022-02-25 09:22:43 : INFO : houdahspot : Installed HoudahSpot, version 6.1.11
2022-02-25 09:22:43 : INFO : houdahspot : notifying
2022-02-25 09:22:43 : INFO : houdahspot : App not closed, so no reopen.
2022-02-25 09:22:43 : INFO : houdahspot :
2022-02-25 09:22:43 : REQ : houdahspot : ################## End Installomator, exit code 0
```
After manually moving Firefox to Utilities I have tested with this:
```
$ sudo /Installomator/utils/assemble.sh firefox DEBUG=0 INSTALL=force
2022-02-09 09:44:04 : INFO : firefox : setting variable from argument DEBUG=0
2022-02-09 09:44:04 : INFO : firefox : setting variable from argument INSTALL=force
2022-02-09 09:44:04 : REQ : firefox : ################## Start Installomator v. 9.1beta, date 2022-02-09
2022-02-09 09:44:04 : INFO : firefox : ################## Version: 9.1beta
2022-02-09 09:44:04 : INFO : firefox : ################## Date: 2022-02-09
2022-02-09 09:44:04 : INFO : firefox : ################## firefox
2022-02-09 09:44:04 : INFO : firefox : BLOCKING_PROCESS_ACTION=tell_user
2022-02-09 09:44:04 : INFO : firefox : NOTIFY=success
2022-02-09 09:44:04 : INFO : firefox : LOGGING=INFO
2022-02-09 09:44:04 : INFO : firefox : LOGO=/System/Applications/App Store.app/Contents/Resources/AppIcon.icns
2022-02-09 09:44:04 : INFO : firefox : Label type: dmg
2022-02-09 09:44:04 : INFO : firefox : targetDir for installation: /Applications/Utilities
2022-02-09 09:44:04 : INFO : firefox : found app at /Applications/Utilities/Firefox.app, version 97.0, on versionKey CFBundleShortVersionString
2022-02-09 09:44:04 : INFO : firefox : appversion: 97.0
2022-02-09 09:44:04 : INFO : firefox : Label is not of type “updateronly”, and it’s set to use force to install or ignoring app store apps, so not using updateTool.
2022-02-09 09:44:04 : INFO : firefox : Latest version of Firefox is 97.0
2022-02-09 09:44:04 : INFO : firefox : There is no newer version available.
2022-02-09 09:44:04 : REQ : firefox : Downloading https://download.mozilla.org/?product=firefox-latest&os=osx&lang=en-US to Firefox.dmg
2022-02-09 09:44:16 : REQ : firefox : no more blocking processes, continue with update
2022-02-09 09:44:16 : REQ : firefox : Installing Firefox
2022-02-09 09:44:16 : INFO : firefox : Mounting /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/tmp.NMItuUfS/Firefox.dmg
2022-02-09 09:44:24 : INFO : firefox : Mounted: /Volumes/Firefox
2022-02-09 09:44:24 : INFO : firefox : Verifying: /Volumes/Firefox/Firefox.app
2022-02-09 09:44:33 : INFO : firefox : Team ID matching: 43AQ936H96 (expected: 43AQ936H96 )
2022-02-09 09:44:33 : INFO : firefox : Downloaded version of Firefox is 97.0 on versionKey CFBundleShortVersionString, same as installed.
2022-02-09 09:44:33 : INFO : firefox : Using force to install anyway.
2022-02-09 09:44:33 : INFO : firefox : App has LSMinimumSystemVersion: 10.12.0
2022-02-09 09:44:33 : INFO : firefox : Copy /Volumes/Firefox/Firefox.app to /Applications/Utilities
2022-02-09 09:44:40 : INFO : firefox : Changing owner to st
2022-02-09 09:44:40 : INFO : firefox : Finishing...
2022-02-09 09:44:50 : INFO : firefox : targetDir for installation: /Applications/Utilities
2022-02-09 09:44:50 : INFO : firefox : found app at /Applications/Utilities/Firefox.app, version 97.0, on versionKey CFBundleShortVersionString
2022-02-09 09:44:50 : INFO : firefox : Installed Firefox, version 97.0
2022-02-09 09:44:50 : INFO : firefox : notifying
2022-02-09 09:44:50 : REQ : firefox : ################## End Installomator, exit code 0
```
The ls command to check for this file will throw an error when the file does not exist. Better to simply test for the file (with size greater than zero).
Will now also go through labels with warnings in the, to figure out if the label works. Many warnings are about version checking, so those will be verified now.
Moved the variable declarations from `functions.sh` to `arguments.sh`. We need the argument parsing before setting the logging level and other variables.
This script will check certain labels. It's meant to check all (or most) of Installomator, to see if the code is working. We need labels that are representative for alle the functionality in the script.
(Bug-fix for LSMinimumSystemVersion is needed for some of these to work)
If `versionKey` is used as part of `valuesfromarguments` it will currently be replaced by our standard value `CFBundleShortVersionString` (it was only testet on labels). So added an `if...then` to know if it was already set as part of the arguments.
Also improved logging to show what `versionKey` is.
When I created PR #374, the sparkle feed had just one entry. Turns out, that Docker uses the last entry of the feed for the latest version.
With simply changing xpath to use `[last()]`, the version checking now behaves as expected.
Improved first lines of logs to be required and show `VERSION` and `VERSIONDATE` on separate lines.
Logging sent to Datadog will have `VERSION` on each line.
URLs for version checking have changed. It's now using the `shortVersionString` from the sparkle feed.
Example run for M1:
```
$ sudo zsh Installomator.sh docker DEBUG=0
2022-01-12 18:16:35 docker setting variable from argument DEBUG=0
2022-01-12 18:16:35 docker ################## Start Installomator v. 8.0
2022-01-12 18:16:35 docker ################## docker
2022-01-12 18:16:35 docker BLOCKING_PROCESS_ACTION=tell_user
2022-01-12 18:16:35 docker NOTIFY=success
2022-01-12 18:16:35 docker LOGO=/System/Applications/App Store.app/Contents/Resources/AppIcon.icns
2022-01-12 18:16:35 docker no blocking processes defined, using Docker as default
2022-01-12 18:16:35 docker Changing directory to /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/tmp.t4N46qTN
2022-01-12 18:16:35 docker App(s) found: /Applications/Docker.app
2022-01-12 18:16:35 docker found app at /Applications/Docker.app, version 4.3.2
2022-01-12 18:16:35 docker appversion: 4.3.2
2022-01-12 18:16:35 docker Latest version of Docker is 4.3.2
2022-01-12 18:16:35 docker There is no newer version available.
2022-01-12 18:16:35 docker Deleting /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/tmp.t4N46qTN
2022-01-12 18:16:35 docker App not closed, so no reopen.
2022-01-12 18:16:35 docker ################## End Installomator, exit code 0
```
Improvements to logging:
- Logging levels as DEBUG 0 INFO 1 WARN 2 ERROR 3 REQ 4
- External logging to Datadog
- A function to shorten duplicate lines in installation logs
- Ability to extract install.log in the time when Installomator was running, if further investigations needs to be done to logs
In `logitechoptions` we do not know what the app-name is that contains the pkg in the bundle-package, so now we only give the name of the pkg, and then Installomator will find it.
Now return one `#` when unknown label is given, not a whole bunch of them.
```
Installomator/utils/assemble.sh strangelabel RETURN_LABEL_NAME=1 DEBUG=0 | tail -1
#
```
Improved buildLabel.sh to handle another set of headers when trying to download, and that can handle the mocha-software.
But mocha-software has been disabled, as Installomator does not offer the headers when that is trying to download.
If an app has `LSMinimumSystemVersion` in the `Info.plist`, then we will check if the installed macOS lives up to this, and exit if not.
First a normal run on Monterey:
```
Installomator/utils/assemble.sh omnidisksweeper DEBUG=0 INSTALL=force
2022-01-07 13:37:43 omnidisksweeper setting variable from argument DEBUG=0
2022-01-07 13:37:43 omnidisksweeper setting variable from argument INSTALL=force
2022-01-07 13:37:43 omnidisksweeper ################## Start Installomator v. 9.0dev
2022-01-07 13:37:43 omnidisksweeper ################## omnidisksweeper
2022-01-07 13:37:44 omnidisksweeper BLOCKING_PROCESS_ACTION=tell_user
2022-01-07 13:37:44 omnidisksweeper NOTIFY=success
2022-01-07 13:37:44 omnidisksweeper LOGO=/System/Applications/App Store.app/Contents/Resources/AppIcon.icns
2022-01-07 13:37:44 omnidisksweeper no blocking processes defined, using OmniDiskSweeper as default
2022-01-07 13:37:44 omnidisksweeper Changing directory to /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/tmp.41qqoUEN
2022-01-07 13:37:44 omnidisksweeper App(s) found: /Applications/OmniDiskSweeper.app
2022-01-07 13:37:44 omnidisksweeper found app at /Applications/OmniDiskSweeper.app, version 1.13
2022-01-07 13:37:44 omnidisksweeper appversion: 1.13
2022-01-07 13:37:44 omnidisksweeper Using force to install, so not using updateTool.
2022-01-07 13:37:44 omnidisksweeper Latest version of OmniDiskSweeper is 1.13
2022-01-07 13:37:44 omnidisksweeper There is no newer version available.
2022-01-07 13:37:44 omnidisksweeper Downloading https://downloads.omnigroup.com/software/MacOSX/10.14/OmniDiskSweeper-1.13.dmg to OmniDiskSweeper.dmg
2022-01-07 13:37:45 omnidisksweeper no more blocking processes, continue with update
2022-01-07 13:37:45 omnidisksweeper Installing OmniDiskSweeper
2022-01-07 13:37:45 omnidisksweeper Mounting /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/tmp.41qqoUEN/OmniDiskSweeper.dmg
2022-01-07 13:37:46 omnidisksweeper Mounted: /Volumes/OmniDiskSweeper
2022-01-07 13:37:46 omnidisksweeper Verifying: /Volumes/OmniDiskSweeper/OmniDiskSweeper.app
2022-01-07 13:37:49 omnidisksweeper Team ID matching: 34YW5XSRB7 (expected: 34YW5XSRB7 )
2022-01-07 13:37:49 omnidisksweeper App has LSMinimumSystemVersion: 10.14
2022-01-07 13:37:49 omnidisksweeper Downloaded version of OmniDiskSweeper is 1.13, same as installed.
2022-01-07 13:37:49 omnidisksweeper Using force to install anyway.
2022-01-07 13:37:49 omnidisksweeper Removing existing /Applications/OmniDiskSweeper.app
2022-01-07 13:37:49 omnidisksweeper Copy /Volumes/OmniDiskSweeper/OmniDiskSweeper.app to /Applications
2022-01-07 13:37:49 omnidisksweeper Changing owner to st
2022-01-07 13:37:49 omnidisksweeper Finishing...
2022-01-07 13:37:59 omnidisksweeper App(s) found: /Applications/OmniDiskSweeper.app
2022-01-07 13:37:59 omnidisksweeper found app at /Applications/OmniDiskSweeper.app, version 1.13
2022-01-07 13:37:59 omnidisksweeper Installed OmniDiskSweeper, version 1.13
2022-01-07 13:37:59 omnidisksweeper notifying
2022-01-07 13:37:59 omnidisksweeper Deleting /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/tmp.41qqoUEN
2022-01-07 13:37:59 omnidisksweeper Unmounting /Volumes/OmniDiskSweeper
"disk4" ejected.
2022-01-07 13:38:00 omnidisksweeper App not closed, so no reopen.
2022-01-07 13:38:00 omnidisksweeper ################## End Installomator, exit code 0
```
Trying where I manually change OS version to 10.13:
```
Installomator/utils/assemble.sh omnidisksweeper DEBUG=0 INSTALL=force
2022-01-07 13:38:39 omnidisksweeper setting variable from argument DEBUG=0
2022-01-07 13:38:39 omnidisksweeper setting variable from argument INSTALL=force
2022-01-07 13:38:39 omnidisksweeper ################## Start Installomator v. 9.0dev
2022-01-07 13:38:39 omnidisksweeper ################## omnidisksweeper
2022-01-07 13:38:39 omnidisksweeper BLOCKING_PROCESS_ACTION=tell_user
2022-01-07 13:38:39 omnidisksweeper NOTIFY=success
2022-01-07 13:38:39 omnidisksweeper LOGO=/System/Applications/App Store.app/Contents/Resources/AppIcon.icns
2022-01-07 13:38:39 omnidisksweeper no blocking processes defined, using OmniDiskSweeper as default
2022-01-07 13:38:39 omnidisksweeper Changing directory to /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/tmp.PXjTfPiA
2022-01-07 13:38:39 omnidisksweeper App(s) found: /Applications/OmniDiskSweeper.app
2022-01-07 13:38:39 omnidisksweeper found app at /Applications/OmniDiskSweeper.app, version 1.13
2022-01-07 13:38:40 omnidisksweeper appversion: 1.13
2022-01-07 13:38:40 omnidisksweeper Using force to install, so not using updateTool.
2022-01-07 13:38:40 omnidisksweeper Latest version of OmniDiskSweeper is 1.13
2022-01-07 13:38:40 omnidisksweeper There is no newer version available.
2022-01-07 13:38:40 omnidisksweeper Downloading https://downloads.omnigroup.com/software/MacOSX/10.14/OmniDiskSweeper-1.13.dmg to OmniDiskSweeper.dmg
2022-01-07 13:38:40 omnidisksweeper no more blocking processes, continue with update
2022-01-07 13:38:40 omnidisksweeper Installing OmniDiskSweeper
2022-01-07 13:38:40 omnidisksweeper Mounting /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/tmp.PXjTfPiA/OmniDiskSweeper.dmg
2022-01-07 13:38:41 omnidisksweeper Mounted: /Volumes/OmniDiskSweeper
2022-01-07 13:38:41 omnidisksweeper Verifying: /Volumes/OmniDiskSweeper/OmniDiskSweeper.app
2022-01-07 13:38:43 omnidisksweeper Team ID matching: 34YW5XSRB7 (expected: 34YW5XSRB7 )
2022-01-07 13:38:43 omnidisksweeper App has LSMinimumSystemVersion: 10.14
2022-01-07 13:38:43 omnidisksweeper App requires higher System Version than installed: 10.13
2022-01-07 13:38:43 omnidisksweeper ERROR: Installed macOS is too old for this app.
2022-01-07 13:38:43 omnidisksweeper Deleting /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/tmp.PXjTfPiA
2022-01-07 13:38:43 omnidisksweeper Unmounting /Volumes/OmniDiskSweeper
"disk4" ejected.
2022-01-07 13:38:43 omnidisksweeper App not closed, so no reopen.
2022-01-07 13:38:43 omnidisksweeper ################## End Installomator, exit code 6
```
When using DEPNotify I would like Installomator to return a nice name for the label to show as status in DEPNotify, instead of only the label name.
This way we can do that.
And maybe in the fute include a description of the software, if people are seeking inspiration to software by looking at Installomator (that contains a lot of preferred solution for many)
Currently (before this patch) a label like `microsoftonedrive` that was installed from App Store, and that we want to replace with the “ordinary” version, Installomator would use updateTool, even though `IGNORE_APP_STORE_APPS=yes`. So we would have to have `INSTALL=force` in order to have the app replaced, as `updateTool` would be used.
With this patch, if `IGNORE_APP_STORE_APPS=yes` then `updateTool` will be not set, and the App Store app would be replaced. But if the installed software was not from App Store, then `updateTool` would not be used, and it would be a kind of a forced install (except if the version is the same).
I have this output:
```
➜ Downloads sudo Installomator/utils/assemble.sh microsoftonedrive DEBUG=0
2021-11-30 10:12:11 microsoftonedrive setting variable from argument DEBUG=0
2021-11-30 10:12:11 microsoftonedrive ################## Start Installomator v. 9.0dev
2021-11-30 10:12:11 microsoftonedrive ################## microsoftonedrive
2021-11-30 10:12:13 microsoftonedrive Running msupdate --list
Checking for updates...
Update Assistant is available.
Update Assistant is checking for updates.
Update Assistant is available.
No updates available
2021-11-30 10:12:27 microsoftonedrive BLOCKING_PROCESS_ACTION=tell_user
2021-11-30 10:12:27 microsoftonedrive NOTIFY=success
2021-11-30 10:12:27 microsoftonedrive LOGO=/System/Applications/App Store.app/Contents/Resources/AppIcon.icns
2021-11-30 10:12:27 microsoftonedrive no blocking processes defined, using OneDrive as default
2021-11-30 10:12:27 microsoftonedrive Changing directory to /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/tmp.5kJ1YWMy
2021-11-30 10:12:27 microsoftonedrive App(s) found: /Applications/OneDrive.app
2021-11-30 10:12:27 microsoftonedrive found app at /Applications/OneDrive.app, version 21.220.1024
2021-11-30 10:12:27 microsoftonedrive Installed OneDrive.app is from App Store, use “IGNORE_APP_STORE_APPS=yes” to replace.
2021-11-30 10:12:27 microsoftonedrive ERROR: App previously installed from App Store, and we respect that
2021-11-30 10:12:27 microsoftonedrive Deleting /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/tmp.5kJ1YWMy
2021-11-30 10:12:27 microsoftonedrive App not closed, so no reopen.
2021-11-30 10:12:27 microsoftonedrive ################## End Installomator, exit code 1
➜ Downloads sudo Installomator/utils/assemble.sh microsoftonedrive DEBUG=0 IGNORE_APP_STORE_APPS=yes
2021-11-30 10:12:50 microsoftonedrive setting variable from argument DEBUG=0
2021-11-30 10:12:50 microsoftonedrive setting variable from argument IGNORE_APP_STORE_APPS=yes
2021-11-30 10:12:50 microsoftonedrive ################## Start Installomator v. 9.0dev
2021-11-30 10:12:50 microsoftonedrive ################## microsoftonedrive
2021-11-30 10:12:51 microsoftonedrive Running msupdate --list
Checking for updates...
Update Assistant is available.
Update Assistant is checking for updates.
Update Assistant is available.
No updates available
2021-11-30 10:13:06 microsoftonedrive BLOCKING_PROCESS_ACTION=tell_user
2021-11-30 10:13:06 microsoftonedrive NOTIFY=success
2021-11-30 10:13:06 microsoftonedrive LOGO=/System/Applications/App Store.app/Contents/Resources/AppIcon.icns
2021-11-30 10:13:06 microsoftonedrive no blocking processes defined, using OneDrive as default
2021-11-30 10:13:06 microsoftonedrive Changing directory to /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/tmp.OXbBLX0y
2021-11-30 10:13:06 microsoftonedrive App(s) found: /Applications/OneDrive.app
2021-11-30 10:13:06 microsoftonedrive found app at /Applications/OneDrive.app, version 21.220.1024
2021-11-30 10:13:06 microsoftonedrive Installed OneDrive.app is from App Store, use “IGNORE_APP_STORE_APPS=yes” to replace.
2021-11-30 10:13:06 microsoftonedrive Replacing App Store apps, no matter the version
2021-11-30 10:13:06 microsoftonedrive appversion: 0
2021-11-30 10:13:06 microsoftonedrive Label is not of type “updateronly”, and it’s set to use force to install or ignoring app store apps, so not using updateTool.
2021-11-30 10:13:06 microsoftonedrive Latest version of OneDrive is 21.205.1003
2021-11-30 10:13:06 microsoftonedrive Downloading https://go.microsoft.com/fwlink/?linkid=823060 to OneDrive.pkg
2021-11-30 10:15:01 microsoftonedrive no more blocking processes, continue with update
2021-11-30 10:15:01 microsoftonedrive Installing OneDrive
2021-11-30 10:15:01 microsoftonedrive Verifying: OneDrive.pkg
2021-11-30 10:15:02 microsoftonedrive Team ID: UBF8T346G9 (expected: UBF8T346G9 )
2021-11-30 10:15:02 microsoftonedrive Installing OneDrive.pkg to /
installer: Package name is Microsoft OneDrive
installer: Upgrading at base path /
installer: The upgrade was successful.
2021-11-30 10:15:08 microsoftonedrive Finishing...
2021-11-30 10:15:18 microsoftonedrive App(s) found: /Applications/OneDrive.app
2021-11-30 10:15:18 microsoftonedrive found app at /Applications/OneDrive.app, version 21.220.1024
2021-11-30 10:15:18 microsoftonedrive Installed OneDrive.app is from App Store, use “IGNORE_APP_STORE_APPS=yes” to replace.
2021-11-30 10:15:18 microsoftonedrive Replacing App Store apps, no matter the version
2021-11-30 10:15:18 microsoftonedrive Installed OneDrive, version 0
2021-11-30 10:15:18 microsoftonedrive notifying
2021-11-30 10:15:18 microsoftonedrive Deleting /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/tmp.OXbBLX0y
2021-11-30 10:15:18 microsoftonedrive App not closed, so no reopen.
2021-11-30 10:15:18 microsoftonedrive ################## End Installomator, exit code 0
```
Now we can call any script on the root of the path where `appName` is found.
Same result:
```
2021-11-10 15:58:02 adobecreativeclouddesktop setting variable from argument DEBUG=0
2021-11-10 15:58:02 adobecreativeclouddesktop setting variable from argument INSTALL=force
2021-11-10 15:58:02 adobecreativeclouddesktop ################## Start Installomator v. 0.8.0
2021-11-10 15:58:02 adobecreativeclouddesktop ################## adobecreativeclouddesktop
2021-11-10 15:58:03 adobecreativeclouddesktop BLOCKING_PROCESS_ACTION=tell_user
2021-11-10 15:58:03 adobecreativeclouddesktop NOTIFY=success
2021-11-10 15:58:03 adobecreativeclouddesktop LOGO=/System/Applications/App Store.app/Contents/Resources/AppIcon.icns
2021-11-10 15:58:03 adobecreativeclouddesktop no blocking processes defined, using Creative Cloud as default
2021-11-10 15:58:03 adobecreativeclouddesktop Changing directory to /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/tmp.WNV7B1pH
2021-11-10 15:58:03 adobecreativeclouddesktop App(s) found: /Library/Application Support/Adobe/Adobe Desktop Common/HDBox/Install.app
2021-11-10 15:58:03 adobecreativeclouddesktop could not determine location of Install.app
2021-11-10 15:58:03 adobecreativeclouddesktop appversion:
2021-11-10 15:58:03 adobecreativeclouddesktop Latest version of Creative Cloud is 5.6.0.788
2021-11-10 15:58:03 adobecreativeclouddesktop Downloading https://ccmdl.adobe.com/AdobeProducts/KCCC/CCD/5_6_0/macarm64/ACCCx5_6_0_788.dmg to Creative Cloud.dmg
2021-11-10 15:58:17 adobecreativeclouddesktop no more blocking processes, continue with update
2021-11-10 15:58:17 adobecreativeclouddesktop Installing Creative Cloud
2021-11-10 15:58:17 adobecreativeclouddesktop Mounting /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/tmp.WNV7B1pH/Creative Cloud.dmg
2021-11-10 15:58:18 adobecreativeclouddesktop Mounted: /Volumes/Creative Cloud
2021-11-10 15:58:18 adobecreativeclouddesktop Verifying: /Volumes/Creative Cloud/Install.app
2021-11-10 15:58:18 adobecreativeclouddesktop Team ID matching: JQ525L2MZD (expected: JQ525L2MZD )
2021-11-10 15:58:18 adobecreativeclouddesktop Downloaded version of Creative Cloud is 2.6.0.46 (replacing version ).
2021-11-10 15:58:18 adobecreativeclouddesktop CLIInstaller exists, running installer command /Volumes/Creative Cloud/Install.app/Contents/MacOS/Install --mode=silent
2021-11-10 15:58:23 adobecreativeclouddesktop Succesfully ran /Volumes/Creative Cloud/Install.app/Contents/MacOS/Install --mode=silent
2021-11-10 15:58:23 adobecreativeclouddesktop Debugging enabled, update tool output was:
objc[20055]: Class HTTPHeader is implemented in both /Volumes/Creative Cloud/Install.app/Contents/MacOS/Install (0x102565018) and /Library/Application Support/Adobe/Adobe Desktop Common/Core/AdobePIM.dylib (0x10f2f0790). One of the two will be used. Which one is undefined.
objc[20055]: Class ProxyManager is implemented in both /Volumes/Creative Cloud/Install.app/Contents/MacOS/Install (0x102565068) and /Library/Application Support/Adobe/Adobe Desktop Common/Core/AdobePIM.dylib (0x10f2f07e0). One of the two will be used. Which one is undefined.
objc[20055]: Class HTTPHeader is implemented in both /Volumes/Creative Cloud/Install.app/Contents/MacOS/Install (0x102565018) and /Volumes/Creative Cloud/resources/AdobePIM.dylib (0x110302790). One of the two will be used. Which one is undefined.
objc[20055]: Class ProxyManager is implemented in both /Volumes/Creative Cloud/Install.app/Contents/MacOS/Install (0x102565068) and /Volumes/Creative Cloud/resources/AdobePIM.dylib (0x1103027e0). One of the two will be used. Which one is undefined.
Starting installer...
Installation successful.
2021-11-10 15:58:23 adobecreativeclouddesktop Finishing…
2021-11-10 15:58:33 adobecreativeclouddesktop App(s) found: /Library/Application Support/Adobe/Adobe Desktop Common/HDBox/Install.app
2021-11-10 15:58:33 adobecreativeclouddesktop could not determine location of Install.app
2021-11-10 15:58:33 adobecreativeclouddesktop Installed Creative Cloud
2021-11-10 15:58:33 adobecreativeclouddesktop notifying
2021-11-10 15:58:33 adobecreativeclouddesktop Deleting /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/tmp.WNV7B1pH
2021-11-10 15:58:33 adobecreativeclouddesktop Unmounting /Volumes/Creative Cloud
"disk5" ejected.
2021-11-10 15:58:33 adobecreativeclouddesktop App not closed, so no reopen.
2021-11-10 15:58:33 adobecreativeclouddesktop ################## End Installomator, exit code 0
```
Changes to the label, so path to CLIInstaller does not contain the name of the app, as that is already in the variable `appPath`.
Still needing to decide on debug logging or what kind of message we want there.
But this is succesfull:
```
% sudo /Users/st/Documents/GitHub/Installomator/utils/assemble.sh -r adobecreativeclouddesktop DEBUG=0 INSTALL=force
Password:
2021-11-10 11:30:51 adobecreativeclouddesktop setting variable from argument DEBUG=0
2021-11-10 11:30:51 adobecreativeclouddesktop setting variable from argument INSTALL=force
2021-11-10 11:30:51 adobecreativeclouddesktop ################## Start Installomator v. 0.8.0
2021-11-10 11:30:51 adobecreativeclouddesktop ################## adobecreativeclouddesktop
2021-11-10 11:30:51 adobecreativeclouddesktop BLOCKING_PROCESS_ACTION=tell_user
2021-11-10 11:30:51 adobecreativeclouddesktop NOTIFY=success
2021-11-10 11:30:52 adobecreativeclouddesktop LOGO=/System/Applications/App Store.app/Contents/Resources/AppIcon.icns
2021-11-10 11:30:52 adobecreativeclouddesktop no blocking processes defined, using Creative Cloud as default
2021-11-10 11:30:52 adobecreativeclouddesktop Changing directory to /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/tmp.wMH45Qfi
2021-11-10 11:30:52 adobecreativeclouddesktop App(s) found: /Library/Application Support/Adobe/Adobe Desktop Common/HDBox/Install.app
2021-11-10 11:30:52 adobecreativeclouddesktop could not determine location of Install.app
2021-11-10 11:30:52 adobecreativeclouddesktop appversion:
2021-11-10 11:30:52 adobecreativeclouddesktop Latest version of Creative Cloud is 5.6.0.788
2021-11-10 11:30:52 adobecreativeclouddesktop Downloading https://ccmdl.adobe.com/AdobeProducts/KCCC/CCD/5_6_0/macarm64/ACCCx5_6_0_788.dmg to Creative Cloud.dmg
2021-11-10 11:31:41 adobecreativeclouddesktop no more blocking processes, continue with update
2021-11-10 11:31:41 adobecreativeclouddesktop Installing Creative Cloud
2021-11-10 11:31:41 adobecreativeclouddesktop Mounting /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/tmp.wMH45Qfi/Creative Cloud.dmg
2021-11-10 11:31:42 adobecreativeclouddesktop Mounted: /Volumes/Creative Cloud 2
2021-11-10 11:31:42 adobecreativeclouddesktop Verifying: /Volumes/Creative Cloud 2/Install.app
2021-11-10 11:31:42 adobecreativeclouddesktop Team ID matching: JQ525L2MZD (expected: JQ525L2MZD )
2021-11-10 11:31:42 adobecreativeclouddesktop Downloaded version of Creative Cloud is 2.6.0.46 (replacing version ).
2021-11-10 11:31:42 adobecreativeclouddesktop CLIInstaller exists, running installer command /Volumes/Creative Cloud 2/Install.app/Contents/MacOS/Install --mode=silent
2021-11-10 11:31:46 adobecreativeclouddesktop Succesfully ran /Volumes/Creative Cloud 2/Install.app/Contents/MacOS/Install --mode=silent
2021-11-10 11:31:46 adobecreativeclouddesktop Debugging enabled, update tool output was:
objc[71312]: Class HTTPHeader is implemented in both /Volumes/Creative Cloud 2/Install.app/Contents/MacOS/Install (0x100c2f018) and /Library/Application Support/Adobe/Adobe Desktop Common/Core/AdobePIM.dylib (0x10dc38790). One of the two will be used. Which one is undefined.
objc[71312]: Class ProxyManager is implemented in both /Volumes/Creative Cloud 2/Install.app/Contents/MacOS/Install (0x100c2f068) and /Library/Application Support/Adobe/Adobe Desktop Common/Core/AdobePIM.dylib (0x10dc387e0). One of the two will be used. Which one is undefined.
objc[71312]: Class HTTPHeader is implemented in both /Volumes/Creative Cloud 2/Install.app/Contents/MacOS/Install (0x100c2f018) and /Volumes/Creative Cloud 2/resources/AdobePIM.dylib (0x10e4e6790). One of the two will be used. Which one is undefined.
objc[71312]: Class ProxyManager is implemented in both /Volumes/Creative Cloud 2/Install.app/Contents/MacOS/Install (0x100c2f068) and /Volumes/Creative Cloud 2/resources/AdobePIM.dylib (0x10e4e67e0). One of the two will be used. Which one is undefined.
Starting installer...
Installation successful.
2021-11-10 11:31:46 adobecreativeclouddesktop Finishing…
2021-11-10 11:31:56 adobecreativeclouddesktop App(s) found: /Library/Application Support/Adobe/Adobe Desktop Common/HDBox/Install.app
2021-11-10 11:31:56 adobecreativeclouddesktop could not determine location of Install.app
2021-11-10 11:31:56 adobecreativeclouddesktop Installed Creative Cloud
2021-11-10 11:31:56 adobecreativeclouddesktop notifying
2021-11-10 11:31:56 adobecreativeclouddesktop Deleting /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/tmp.wMH45Qfi
2021-11-10 11:31:56 adobecreativeclouddesktop Unmounting /Volumes/Creative Cloud 2
"disk6" ejected.
2021-11-10 11:31:57 adobecreativeclouddesktop App not closed, so no reopen.
2021-11-10 11:31:57 adobecreativeclouddesktop ################## End Installomator, exit code 0
```
I was looking into installing Adobe CC fully (Isaac has done the hard part), and we can add `CLIInstaller` and `CLIArguments` to get it fully installed.
This implementation is slightly changed from Isaacs.
```
% sudo /Users/st/Documents/GitHub/Installomator/utils/assemble.sh -r adobecreativeclouddesktop DEBUG=0 INSTALL=force
2021-11-10 08:56:00 adobecreativeclouddesktop setting variable from argument DEBUG=0
2021-11-10 08:56:00 adobecreativeclouddesktop setting variable from argument INSTALL=force
2021-11-10 08:56:00 adobecreativeclouddesktop ################## Start Installomator v. 0.8.0
2021-11-10 08:56:00 adobecreativeclouddesktop ################## adobecreativeclouddesktop
2021-11-10 08:56:00 adobecreativeclouddesktop BLOCKING_PROCESS_ACTION=tell_user
2021-11-10 08:56:00 adobecreativeclouddesktop NOTIFY=success
2021-11-10 08:56:00 adobecreativeclouddesktop LOGO=/System/Applications/App Store.app/Contents/Resources/AppIcon.icns
2021-11-10 08:56:00 adobecreativeclouddesktop no blocking processes defined, using Creative Cloud as default
2021-11-10 08:56:00 adobecreativeclouddesktop Changing directory to /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/tmp.0LNrXCQX
2021-11-10 08:56:01 adobecreativeclouddesktop App(s) found: /Library/Application Support/Adobe/Adobe Desktop Common/HDBox/Install.app
2021-11-10 08:56:01 adobecreativeclouddesktop could not determine location of Install.app
2021-11-10 08:56:01 adobecreativeclouddesktop appversion:
2021-11-10 08:56:01 adobecreativeclouddesktop Latest version of Creative Cloud is 5.6.0.788
2021-11-10 08:56:01 adobecreativeclouddesktop Downloading https://ccmdl.adobe.com/AdobeProducts/KCCC/CCD/5_6_0/macarm64/ACCCx5_6_0_788.dmg to Creative Cloud.dmg
2021-11-10 08:56:30 adobecreativeclouddesktop no more blocking processes, continue with update
2021-11-10 08:56:30 adobecreativeclouddesktop Installing Creative Cloud
2021-11-10 08:56:30 adobecreativeclouddesktop Mounting /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/tmp.0LNrXCQX/Creative Cloud.dmg
2021-11-10 08:56:30 adobecreativeclouddesktop Mounted: /Volumes/Creative Cloud
2021-11-10 08:56:30 adobecreativeclouddesktop Verifying: /Volumes/Creative Cloud/Install.app
2021-11-10 08:56:30 adobecreativeclouddesktop Team ID matching: JQ525L2MZD (expected: JQ525L2MZD )
2021-11-10 08:56:30 adobecreativeclouddesktop Downloaded version of Creative Cloud is 2.6.0.46 (replacing version ).
2021-11-10 08:56:30 adobecreativeclouddesktop CLIInstaller exists, running installer command /Volumes/Creative Cloud/Install.app/Contents/MacOS/Install --mode=silent
2021-11-10 08:56:34 adobecreativeclouddesktop Debugging enabled, update tool output was: objc[51900]: Class HTTPHeader is implemented in both /Volumes/Creative Cloud/Install.app/Contents/MacOS/Install (0x102d2a018) and /Library/Application Support/Adobe/Adobe Desktop Common/Core/AdobePIM.dylib (0x10fa75790). One of the two will be used. Which one is undefined.
objc[51900]: Class ProxyManager is implemented in both /Volumes/Creative Cloud/Install.app/Contents/MacOS/Install (0x102d2a068) and /Library/Application Support/Adobe/Adobe Desktop Common/Core/AdobePIM.dylib (0x10fa757e0). One of the two will be used. Which one is undefined.
objc[51900]: Class HTTPHeader is implemented in both /Volumes/Creative Cloud/Install.app/Contents/MacOS/Install (0x102d2a018) and /Volumes/Creative Cloud/resources/AdobePIM.dylib (0x110a87790). One of the two will be used. Which one is undefined.
objc[51900]: Class ProxyManager is implemented in both /Volumes/Creative Cloud/Install.app/Contents/MacOS/Install (0x102d2a068) and /Volumes/Creative Cloud/resources/AdobePIM.dylib (0x110a877e0). One of the two will be used. Which one is undefined.
Starting installer...
Installation successful.
2021-11-10 08:56:34 adobecreativeclouddesktop Finishing…
2021-11-10 08:56:44 adobecreativeclouddesktop App(s) found: /Library/Application Support/Adobe/Adobe Desktop Common/HDBox/Install.app
2021-11-10 08:56:44 adobecreativeclouddesktop could not determine location of Install.app
2021-11-10 08:56:44 adobecreativeclouddesktop Installed Creative Cloud
2021-11-10 08:56:44 adobecreativeclouddesktop notifying
2021-11-10 08:56:44 adobecreativeclouddesktop Deleting /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/tmp.0LNrXCQX
2021-11-10 08:56:44 adobecreativeclouddesktop Unmounting /Volumes/Creative Cloud
"disk4" ejected.
2021-11-10 08:56:45 adobecreativeclouddesktop App not closed, so no reopen.
2021-11-10 08:56:45 adobecreativeclouddesktop ################## End Installomator, exit code 0
```
If `INSTALL=force` is used, then previously we would need installed version and appNewVersion to be equal for the updateTool to be skipped. Not anymore.
Separate lines for running `msupdate --list` before running the update tool, but currently it runs if just msupdate exist, and not only if we run the updateTool.
By using variable `archiveName` we can let Installomator find the right archive in the github list of possibilities. I think this is a more cleaner approach.
Added a bit to explanation of archiveName variable.
```
sudo /Users/st/Documents/GitHub/Installomator/utils/assemble.sh -r macports DEBUG=0 INSTALL=force
Password:
2021-11-02 09:55:12 macports setting variable from argument DEBUG=0
2021-11-02 09:55:12 macports setting variable from argument INSTALL=force
2021-11-02 09:55:12 macports ################## Start Installomator v. 0.8.0
2021-11-02 09:55:12 macports ################## macports
2021-11-02 09:55:13 macports BLOCKING_PROCESS_ACTION=tell_user
2021-11-02 09:55:13 macports NOTIFY=success
2021-11-02 09:55:14 macports LOGO=/System/Applications/App Store.app/Contents/Resources/AppIcon.icns
2021-11-02 09:55:14 macports no blocking processes defined, using MacPorts as default
2021-11-02 09:55:14 macports Changing directory to /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/tmp.4KnOGDkl
2021-11-02 09:55:14 macports Custom App Version detection is used, found 2.7.1
2021-11-02 09:55:14 macports appversion: 2.7.1
2021-11-02 09:55:14 macports Latest version of MacPorts is 2.7.1
2021-11-02 09:55:14 macports There is no newer version available.
2021-11-02 09:55:14 macports Using force to install anyway. Not using updateTool.
2021-11-02 09:55:14 macports Downloading https://github.com/macports/macports-base/releases/download/v2.7.1/MacPorts-2.7.1-12-Monterey.pkg to Monterey.pkg
2021-11-02 09:55:15 macports no more blocking processes, continue with update
2021-11-02 09:55:15 macports Installing MacPorts
2021-11-02 09:55:16 macports Verifying: Monterey.pkg
2021-11-02 09:55:16 macports Team ID: QTA3A3B7F3 (expected: QTA3A3B7F3 )
2021-11-02 09:55:16 macports Installing Monterey.pkg to /
installer: Package name is MacPorts
installer: Upgrading at base path /
installer: The upgrade was successful.
2021-11-02 09:56:03 macports Finishing…
2021-11-02 09:56:13 macports Custom App Version detection is used, found 2.7.1
2021-11-02 09:56:13 macports Installed MacPorts, version 2.7.1
2021-11-02 09:56:13 macports notifying
2021-11-02 09:56:14 macports Deleting /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/tmp.4KnOGDkl
2021-11-02 09:56:14 macports App not closed, so no reopen.
2021-11-02 09:56:14 macports ################## End Installomator, exit code 0
```
Moved the root user check to the beginning of the script, but added in debug
mode 2 to allow for the kinds of testing you used to be able to do when running
the program in debug 0 as a non-root user. Resolves issue 88
Root user check is now moved from the installation function to main. The new
location is after parsing the label but before printing the log for blocking
process and notify settings. This prevents a downloading an application
that can't be installed.
Resolves issue #88
And everything from the betas ([beta1](https://github.com/Installomator/Installomator/releases/tag/v10beta1), [beta2](https://github.com/Installomator/Installomator/releases/tag/v10beta2), [beta3](https://github.com/Installomator/Installomator/releases/tag/v10beta3))
- new labels:
- ibmnotifier (#716)
- ipvisionconnect (#749)
- logitechoptionsplus (#719)
- lucidlink (#722)
- mactex (#685)
- onscreencontrol (#581)
- projectplace (#688)
- subethaedit (#728)
- sublimemerge (#729)
- venturablocker (#712)
- vysor (#710)
- updated labels:
- googleadseditor (#739)
- openvpnconnectv3 (#750)
- tunnelblick (#618)
## v10beta3
- option to add item to dock if dockutil is installed (#701 requires dockutil https://github.com/kcrawford/dockutil )
- further improvements to GitHub downloads (#691)
- updated user dialog when app is already on the latest version (#658)
Plus everything from beta1 and beta2.
- new labels:
- adobeacrobatprodc (#707)
- adobereaderdc-install (#707)
- archiwareb2go (#625, #707)
- archiwarepst (#624)
- bitrix24 (#661)
- charles (#670)
- chronoagent (#617)
- chronosync (#616)
- cytoscape (#689)
- egnytecore (#655)
- fellow (#599)
- filemakerpro (#609)
- fujifilmwebcam (#598)
- gfxcardstatus (#690)
- horos (#610)
- inetclearreportsdesigner (#601)
- jdk18 (#608)
- latexit (#684)
- nudgesuite (#633)
- origin (#662)
- parallelsrasclient (#607)
- polylens (#671)
- splashtopbusiness (#660)
- tailscale (#620)
- zoomoutlookplugin (#656)
- zotero (#634)
- zulujdk18 (#612)
- updated labels:
- acroniscyberprotectconnectagent (#678)
- adobecreativeclouddesktop (#687)
- adobereaderdc-update (#707)
- audacity (#708)
- duckduckgo (#704)
- libreoffice (#605)
- nudge
- obs (#692)
- r (#702)
- rstudio (#702)
- screamingfrogseospider (#665)
- vlc (#705, #606)
- xcreds
## v10beta2
- fixed problem with GitHub labels (#659)
- bz2 archive support (#659)
- fixed WorkspaceOne support (#653)
- updated how `aapNewVersion` is determined (#680)
- [swiftDialog](https://github.com/bartreardon/swiftDialog) integration (#641, #632), many thanks to @bartreardon, [sample scripts](in the MDM folder)
- added WorkspaceOne option for LOGO (#517)
- added function for JSON parsing with JXA (#529)
- updated assemble.sh script to update Labels.txt when script is rebuilt (#540)
- added a no requisite install script (#493)
- GitHub lookup now don't use API calls, this should avoid or at least reduce rate limiting (#543)
- fixed redundant exit codes (#643, #561)
NOTE: some exit codes have changed! see [Installomator Exit Codes](https://github.com/Installomator/Installomator/wiki/Installomator-Exit-Codes) for a list
- new labels:
- bluejeanswithaudiodriver (#473)
- duodevicehealth (#548)
- googlechromeenterprise (#532)
- ipswupdater (#545)
- mmhmm (#571)
- nordlayer (#419)
- prune (#538)
- whatroute (#560)
- updated labels:
- blender (#535, #622)
- camtasia2019 (#547)
- clickshare (#565)
- egnyte (#500)
- googledrive (#563)
- grammarly (#576)
- marathon, marathon2, marathoninfinity (#544)
- miro (#475, #539)
- notion (#566)
- ringcentralapp (#550)
- sublimetext (#593, #578, #567, #623, #626)
- talkdeskcallbar (#536)
- talkdeskcxcloud (#537)
- wireshark (#585)
## v9.2
**Note**: Both Google and Mozilla recommend using the pkg installers instead of the dmg downloads for managed deployments. So far, Installomator has provided labels for both. (`googlechrome` and `googlechromepkg` or `firefox` and `firefoxpkg`, respectively) Since there are problems with the dmg downloads, a future release of Installomator will _disable_ the `firefox` and `googlechrome` dmg labels. You should switch to using `googlechromepkg` and `firefoxpkg` labels instead.
- added option for Microsoft Endpoint Manager (Intune) to `LOGO` (#446)
- minor fixes (#427, #434, #436)
- the `googlechrome` label now always downloads the universal version (#430)
- new labels:
- 1passwordcli (#429)
- amazoncorretto8jdk (#423)
- autodeskfusion360admininstall (#447)
- axurerp10 (#439)
- calcservice (#426)
- clipy (#412)
- dockutil (#432)
- easyfind (#426)
- grammarly (#444)
- houdahspot (#426)
- macadminspython (#431)
- microsoftazuredatastudio (#438)
- nanosaur (#426)
- tembo (#426)
- wordservice (#426)
- xmenu (#426)
- updated labels:
- appcleaner (#428)
- dialog (#435, #437)
- googlechrome (#430)
- microsoftdefender (#440)
- supportapp (#426)
- zoom and zoomgov (#426, #433)
## v9.0.1
- improved logging levels throughout the script #408
- fixed a bug for `pkgindmg` style labels #408
- changed the criteria used to locate an app in the case the it cannot be found in the default locations, this should help with some apps with similar name (Virtual Box and Box Drive, #401) #413
- new label: WhiteBox Packages (`packages`) #415
- modified label: `loom` (added Apple silicon download) #417
## v9
- We have moved the root check to the beginning of the script, and improved DEBUG handling with two different modes. `DEBUG=0` is still for production, and `1` is still for the DEBUG we previously knew downloading to the directory it is running from, but `2` will download to temporary folder, will detect updates, but will not install anything, but it will notify the user (almost as running the script without root before).
- Added option to not interrupt Do Not Disturb full screen apps like Keynote or Zoom with `INTERRUPT_DND="no"`. Default is `"yes"` which is how it has worked until now.
-`pkgName` in a label can now be searched for. An example is logitechoptions, where only the name of the pkg is given, and not the exact file path to it.
-`LSMinimumSystemVersion` will now be honered, if the `Info.plist` in the app is specifying this. That means that an app that has this parameter in that file and it shows that the app requires a newer version of the OS than is currently installed, then we will not install it.
- New variable `RETURN_LABEL_NAME`. If given the value `1`, like `RETURN_LABEL_NAME=1` then Installomator only returns the name of the label. It makes for a better user friendly message for displaying in DEPNotify if that is integrated.
- Changed logic if `IGNORE_APP_STORE_APPS=yes`. Before this version a label like `microsoftonedrive` that was installed from App Store, and that we want to replace with the “ordinary” version, Installomator would still use `updateTool`, even though `IGNORE_APP_STORE_APPS=yes`. So we would have to have `INSTALL=force` in order to have the app replaced, as `updateTool` would be used. But now if `IGNORE_APP_STORE_APPS=yes` then `updateTool` will be not set, and the App Store app will be replaced. BUT if the installed software was not from App Store, then `updateTool` will not be used, and it would be a kind of a forced install (in the example of `microsoftonedrive`), except if the version is the same (where installation is skipped).
- Added variable `SYSTEMOWNER` that is used when copying files when installing. Default `0` is to change owner of the app to the current user on the Mac, like this user was installing this app themselves. When using `1` we will put “root:wheel” on the app, which can be useful for shared machines.
- Added option `curlOptions` to the labels. It can be filled with extra headers need for downloading the specific software. It needs to be an array, like `curlOptions=( )`. See “mocha”-software-labels.
Big changes to logging:
- Introducing variable `LOGGING`, that can be either of the logging levels
- Logging levels:
0: DEBUG Everything is logged
1: INFO Normal logging behavior
2: WARN
3: ERROR
4: REQ
- External logging to Datadog
- A function to shorten duplicate lines in installation logs or output of longer commands
- Ability to extract install.log in the time when Installomator was running, if further investigations needs to be done to logs
Fixes:
- Fixed a problem with pkgs: If they were mounted with .pkg in the name, then we would find the directory and not the pkg file itself.
- Minor fix for a check for a pkgName on a DMG. We used `ls` that would throw an error when not found, so the check was corrected.
## v8.0
- removed leading `0` from the version because it has lost all meaning (thanks to @grahampugh for the inspiration)
- Installomator now detects when an app is already installed, and will display notifications correctly the user based on if the app was updated or installed for the first time.
- New variables for labels that should be installed using CLI: `CLIInstaller` and `CLIArguments`. When the installer app is named differently than the installed app, then the variable `installerTool` should be used to name the app that should be located in the DMG or zip. See the label __adobecreativeclouddesktop__ to see its use.
-`buildLabel.sh` has been improved to build GitHub software labels much easier. In essense if the URL contains github.com, then it will try to find if it's the latest version or if variable `archiveName` is needed for finding the software. Also improved messaging throughout the script, as well as handling a situation where a pkg does not include a “Distribution” file, but a “PackageInfo”.
- MDM script extended with `caffeinate` so Mac will not go to sleep during the time it takes installomator to run. Especially during setup, this can be useful.
- Microsoft labels with `updateTool` variable, is updated to run `msupdate --list` before running the updateTool directly. Problems have been reported that the update would fail if the `--list` parameter for the command was not run first. This should help with the Jamf agent stalling during installation.
- Added bunch of new labels, and improved others.
## v0.7
- default for `BLOCKING_PROCESS_ACTION`is now `BLOCKING_PROCESS_ACTION=tell_user` and not `prompt_user`. It will demand the user to quit the app to get it updated, and not present any option to skip it. In considering various use cases in different MDM solutions this is the best option going forward. Users usually choose to update, and is most often not bothered much with this information. If it's absoultely a bad time, then they can move the dialog box to the side, and click it when ready.
- script is now assembled from fragments. This helps avoid merging conflicts on git and allows the core team to work on the script logic while also accepting new labels. See the "Assemble Script ReadMe" for details.
- We now detect App Store installed apps, and we do not replace them automatically. An example is Slack that will loose all settings if it is suddenly changed from App Store version to the "web" version (they differ in the handling of settings files). If `INSTALL=force` then we will replace the App Store app. We log all this.
- Change in finding installed apps. We now look in /Applications and /Applications/Utilities first. If not found there, we use spotligt to find it. (We discovered a problem when a user has Parallels Windows installed with Microsoft Edge in it. Then Installomator wanted to update the app all the time, becaus spotligt found that Windows version of the app that Parallels created.)
- Change in finding installed apps. We now look in /Applications and /Applications/Utilities first. If not found there, we use spotligt to find it. (We discovered a problem when a user has Parallels Windows installed with Microsoft Edge in it. Then Installomator wanted to update the app all the time, becaus spotlight found that Windows version of the app that Parallels created.)
- Added bunch of new labels, and improved others.
- Renamed `buildCaseStatement.sh` to `buildLabel.sh` and improved it a lot. It is a great start when figuring out how to create a new label for an app, or a piece of software. Look at the tutorials in our wiki.
- Mosyle changed their app name from Business to Self-Service
__Please note, that if you are contributing to this project with new labels or other suggestions in PRs, please put your changes in the files in the `fragments` sub-folder. DO NOT edit the full `Installomator.sh` script. The full script is generated from the fragments, and will be overwritten. More details on [how the script is assembled from the fragments here](https://github.com/Installomator/Installomator/tree/main/utils#how-to-assemble-installomatorsh).__
We try to keep the script as short as possible, and with more than 400 labels, we can save 400 lines in the script, if we do not have credit lines on each of these. So we are thankful for your contribution, but we will be removing these lines in the coming releases.
## Branches
The branch list is as follows:
-`release`: this branch will have the latest released version
-`main`: (default) this branch will be the current build we are working on. It includes new and updated app labels, and critical bug fixes
-`dev`: this will contain new and updated app labels, as well as other code changes that have the risk of significantly changing or breaking behavior
there will be other branches for new features and testing.
This should allow the contributing team to release minor updates for new and updated app labels while also work on new features for the next major release.
With all the new branches, your local repo may get confused. If you don’t have local changes, it is easiest to delete your local repo and re-clone it. If you have local changes you want to preserve, then you should commit those to a local branch, pull the latest changes `git pull --all`, then delete the old master branch: `git branch -d master`.
Please make sure you branch off of main for your PRs.
__Thank you for contributing!__
## Labels
If you need a new label for a piece of software, please take a look [at the tutorials in the Wiki](https://github.com/Installomator/Installomator/wiki#tutorials), those can be helpful for starting out on the creation of the label.
We expect you to try out finding the __version__ of the software online, so that `appNewVersion` can be filled in the label. It helps a lot when the software needs update, and greatly improve user experience.
Please document what you found out about the __version__ of the software if it's not included. We will not accept a new label if this is not documented, we will ask about this if it was not included. This is very important for the quality and reliability of Installomator.
When creating a new label, please file a pull request (PR). And feel free to ask questions or make your comments about what else is needed, if we should take a look at the label, or help out in finding the version or isolating URLs or anything else. You can find [a tutorial on how to create a PR here](https://github.com/Installomator/Installomator/wiki/GitHub-howto-create-PRs).
Please include the log of installing this label in the description, like this:
Please have one label per PR, so we can separate these. Also if you change/fix a label.
__Thank you very much for your contribution!__
## Issues
Do not create an issue just when you have a questions, but do file an issue or pull request (PR) for bugs or wrong behavior. Include the full log and include the version of Installomator you're running. When you create a PR to follow-up and solve an issue make sure to [mention the issue using the `#xxx` syntax in a commit message or comment to link the issue](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue).
Join [the MacAdmins Slack](https://macadmins.org) and find us in the `#installomator` channel for questions, support and discussions.
When in doubt, use the MacAdmins.org Slack as described in [README.md](https://github.com/Installomator/Installomator/)
# v. 9.6 : 2022-11-15 : GitHub API call is first, only try alternative if that fails.
# v. 9.5 : 2022-09-21 : change of GitHub download
# v. 9.4 : 2022-09-14 : downloadURL can fall back on GitHub API
# v. 9.3 : 2022-08-29 : installomatorOptions in quotes and ignore blocking processes. Improved installation with looping if it fails, so it can try again. Improved GitHub handling. ws1 support.
# v. 9.2.2 : 2022-06-17 : installomatorOptions introduced. Check 1.1.1.1 for internet connection.
# v. 9.2.1 : 2022-05-30 : Some changes to logging
# v. 9.2 : 2022-05-19 : Built in installer for Installlomator, and display dialog if error happens. Now universal script for all supported MDMs based on LOGO variable.
# v. 9.1 : 2022-04-13 : Using INSTALL=force in Label only, so Microsoft labels will not start updating
# v. 9.0.1 : 2022-02-21 : LOGO=addigy, few more "true" lines, and errorOutput on error
# v. 9.0.0 : 2022-02-14 : Updated for Inst. 9.0, Logging improved with printlog
# v. 9.6 : 2022-11-15 : GitHub API call is first, only try alternative if that fails.
# v. 9.5 : 2022-09-21 : change of GitHub download
# v. 9.4 : 2022-09-14 : Making error message optional. downloadURL can fall back on GitHub API.
# v. 9.3 : 2022-08-29 : installomatorOptions in quotes and ignore blocking processes. Improved installation with looping if it fails, so it can try again. Improved GitHub handling. ws1 support.
# v. 9.2.2 : 2022-06-17 : installomatorOptions introduced. Check 1.1.1.1 for internet connection.
# v. 9.2.1 : 2022-05-30 : Some changes to logging
# v. 9.2 : 2022-05-19 : Built in installer for Installomator, and display dialog if error happens. Now universal script for all supported MDMs based on LOGO variable.
# v. 9.6 : 2022-11-15 : GitHub API call is first, only try alternative if that fails.
# v. 9.5 : 2022-09-21 : change of GitHub download
# v. 9.4 : 2022-09-14 : downloadURL can fall back on GitHub API
# v. 9.3 : 2022-08-29 : installomatorOptions in quotes and ignore blocking processes. Improved installation with looping if it fails, so it can try again. Improved GitHub handling. ws1 support.
# v. 9.2.2 : 2022-06-17 : installomatorOptions introduced. Check 1.1.1.1 for internet connection.
# v. 9.2.1 : 2022-05-30 : Some changes to logging
# v. 9.2 : 2022-05-19 : Built in installer for Installlomator, and display dialog if error happens. Now universal script for all supported MDMs based on LOGO variable.
# v. 9.1 : 2022-04-13 : Using INSTALL=force in Label only, so Microsoft labels will not start updating
# v. 9.0.1 : 2022-02-21 : LOGO=addigy, few more "true" lines, and errorOutput on error
# v. 9.0.0 : 2022-02-14 : Updated for Inst. 9.0, Logging improved with printlog
# v. 9.6 : 2022-11-15 : GitHub API call is first, only try alternative if that fails.
# v. 9.5 : 2022-09-21 : change of GitHub download
# v. 9.4 : 2022-09-14 : Making error message optional. downloadURL can fall back on GitHub API.
# v. 9.3 : 2022-08-29 : installomatorOptions in quotes and ignore blocking processes. Improved installation with looping if it fails, so it can try again. Improved GitHub handling. ws1 support.
# v. 9.2.2 : 2022-06-17 : installomatorOptions introduced. Check 1.1.1.1 for internet connection.
# v. 9.2.1 : 2022-05-30 : Some changes to logging
# v. 9.2 : 2022-05-19 : Built in installer for Installomator, and display dialog if error happens. Now universal script for all supported MDMs based on LOGO variable.
# PREVENT Installomator 1st Auto-install from running
# DESCRIPTION
# Will create the file to prevent Installomator 1st Auto-install from running.
# Only for MDM solutions (like Addigy and Microsoft) that have conditions for runnning scripts and do not offer an enrollment event for runnning the script.
# By runninng this script, the file will be created on the client, that will prevent Installomator 1st Auto-install from runnning.
# This is a great help for implementing Installomator 1st Auto-install in a running solution, where the command below have to be run on currently enrolled devices, and then Installomator 1st Auto-install can be assigned to all machines, and will run only on newly enrolled devices.
# Display Installomator Progress with SwiftDialog in Jamf
Installomator 10 has functionality to communicate with [Bart Reardon's swiftDialog](https://github.com/bartreardon/swiftDialog). When you set the `DIALOG_CMD_FILE` variable Installomator will write progress for downloads and installation (with pkgs) to the command file which allows swiftDialog to display the progress.
However, you have to launch and setup swiftDialog to display a window with a progress bar before Installomator launches and also make sure swiftDialog quits after Installomator has run. This may seem complex at first but allows to configure swiftDialog just for your case without needing to modify the Installomator script.
Here are some example script that would run before and after Installomator to display a swiftDialog window and quit the process after. Since Jamf Pro executes scripts in alphanumerical order, the names are chosen accordingly, to ensure proper order.
## Setup in Jamf Pro
To show Installomator progress with swiftDialog from a Jamf Policy, you require three scripts:
-`00_Prepare_SwiftDialog.sh`: Configures and displays the swiftDialog window
-`Installomator.sh`: (v10 or higher)
-`zz_Quit_SwiftDialog.sh`: quits swiftDialog
Add these three scripts to your Jamf Pro and create a policy with these three scripts. The names are chosen that the script appear in the correct order. If you rename the scripts in Jamf Pro, this may disrupt the order and the workflow will not work anymore. The "Priority" of the scripts in the policy should all be the same value.
The different scripts require a set of parameters. We will use the `googlechromepkg` label as an example.
`00_Prepare_SwiftDialog.sh`
Parameter 4: `/var/tmp/dialog.log` (Path to the swiftDialog command file)
Parameter 5: `Installing Google Chrome...` (text shown in the swiftDialog window above the progress bar)
Parameter 6: Path to or URL for an icon in swiftDialog. This can be a path on the client or a URL. See Dan Snelson's advice on how to get icon URLs for Self Service icons: https://rumble.com/v119x6y-harvesting-self-service-icons.html
`Installomator.sh`
Parameter 4: `googlechromepkg` (the label to install)
Parameter 5: `DIALOG_CMD_FILE=/var/tmp/dialog.log` (the swiftDialog command file, this has to be the same value as parameter 4 in the previous script)
You can add more configurations to the Installomator script when needed.
`zz_Quit_SwiftDialog`
Parameter 4: `/var/tmp/dialog.log` (the swiftDialog command file, this has to be the same value as parameter 4 in the first script)
Then setup the remainder of the Jamf Policy to your needs. This works best with Self Service policies.
When you run the policy, the first script will configure and display swiftDialog. Installomator.sh will download and install the app while writing the proper update commands to the file set in `DIALOG_CMD_FILE`. The final script will quit swiftDialog.
# Will create the file to prevent Progress 1st swiftDialog from running.
# Only for MDM solutions (like Addigy and Microsoft) that have conditions for runnning scripts and do not offer an enrollment event for runnning the script.
# By runninng this script, the file will be created on the client, that will prevent Progress 1st swiftDialog from runnning.
# This is a great help for implementing Progress 1st swiftDialog in a running solution, where the command below have to be run on currently enrolled devices, and then Progress 1st swiftDialog can be assigned to all machines, and will run only on newly enrolled devices.
# v. 9.6 : 2022-11-15 : GitHub API call is first, only try alternative if that fails.
# v. 9.5 : 2022-09-21 : change of GitHub download
# v. 9.4 : 2022-09-14 : downloadURL can fall back on GitHub API
# v. 9.3 : 2022-08-29 : Logging changed for current version. Improved installation with looping if it fails, so it can try again. Improved GitHub handling.
# v. 9.2.2 : 2022-06-17 : Improved Dialog installation. Check 1.1.1.1 for internet connection.
# v. 9.2 : 2022-05-19 : Not using GitHub api for download of Dialog, show a dialog when finished to make message more important. Now universal script for all supported MDMs based on LOGO variable.
# v. 9.0 : 2022-05-16 : Based on acodega’s work, I have added progress bar, changed logging and use another log-location, a bit more error handling for Dialog download, added some "|| true"-endings to some lines to not make them fail in Addigy, and some more.
These example scripts are meant for use with MDM to run __Installomator__ and process installs. Examples are also included which use swiftDialog to provide user feedback and dockutil to add app icons to the dock.
There are basically two ways to use Installomator with MDM. The _“Jamf way”_ is where, through the MDM admin interface, your upload the Installomator script to a policy, and you provide additional parameters in the policy configuration like which app to install. The _“other way”_ to use Installomator is by having the MDM install Installomator locally on the computer, just once, and then on subsequent runs the MDM runs a script which calls Installomator and provides the parameters.
Examples of MDMs which use the “other way” are Mosyle Manager/Mosyle Business, Addigy, and Microsoft Endpoint Manager (Intune).
The scripts utilizing __swiftDialog__ require version 10 of __Installomator__. If Installomator version 9 is installed, it will set `NOTIFY=all` and use the traditional __Installomator__ notifications for showing progress, where as on version 10 it will be `NOTIFY=silent` as __swiftDialog__ is used instead.
## Abbreviations used in script names
- SS — Self Service — scripts designed for use through a Self Service catalog
- VFA — valuesfromarguments — a custom label call to Installomator. When using an MDM and the "other way", you can use these scripts to provide the label variables to Installomator for custom labels.
## Condition scripts
Scripts with the `condition` suffix are for use with MDMs like Addigy, where a script is run to determine if the rest of the policy should run.
## Prevention scripts
The `Installomator 1st` and `Progress 1st` scripts are meant to run automatically upon device enrollment. They check for the existance of a file, `/var/db/.Installomator1stDone`, to determine whether the computer has already been deployed. You can run the prevention scripts on existing Macs to ensure the 1st scripts won't inadvertently run on them.
## "Jamf" folder
This folder has Jamf specific examples using __swiftDialog__ as part of the Installomator installation. Perfect for use with Jamf Self Service. Separate [ReadMe-file](Jamf/ReadMe.md) in this folder.
# Scripts to install prerequisites
Use these scripts to handle installing Installomator itself. Additionally, you may want to install swiftDialog manually instead of having Installomator install it.
-`install Installomator direct.sh` — can be run at enrollment and as maintenance at any time to install __Installomator__.
-`install swiftDialog direct.sh` — can be used at enrollment and as maintenance at any time to install __swiftDialog__.
Once Installomator has been installed, __dockutil__ can be installed by Installomator, using this script:
-`App-install/App service Auto-install.sh` — This script uses pre-installed installomator to install __dockutil__.
# Enrollment scripts
For enrollment purposes, some 1st-scripts has been created. One runs silently, another is using __DEPNotify__ to show progress and feedback:
-`Installomator 1st Auto-install DEPNotify.sh` — will install __DEPNotify__ first, start that up, and change progress on the installation bar at each installed label. Very good for Addigy an Microsoft.
-`Installomator 1st Auto-install.sh` — runnning silently installing Installomator labels in the given order. Can be used in combination with the Progress-script.
-`Progress 1st swiftDialog.sh` — It will install __swiftDialog__ and start that up with a list of software it will look for. It will look for an installed file/folder in the file system for each item. This is great if some apps are being installed outside of Installomator, like by Apple Apps & Books, and then this script can show when it has been installed.
There are also Self Service versions of the above.
## “App-install”-folder
- App browser-security Auto-install.sh
- App browser-security SS.sh
- App normal Auto-install.sh
- App normal SS.sh
- App service Auto-install.sh
- App VFA.sh
Here you can use scripts for Self Service (SS) or for Auto-install. There will be a difference in how many notifications will be used and maybe handling of blocking processes.
`browser-security`: For an app like a web browser, you’ll want the install performed right away, so there isn’t a deferral option.
`normal`: The user can defer/skip the update.
`service`: These are apps where we don’t need to ask the user to allow the update. Menu bar apps and utilities would fall under this category.
## “App-install SS with swiftDialog and dockutil”-folder
- App browser-security SS.sh
- App normal SS multi-app.sh
- App normal SS.sh
- App service SS.sh
- App VFA SS github.sh
- App VFA SS.sh
These scripts are similar to the App-install folder but also utilize __swiftDialog__ to show user feedback and installation status, and they also have an option to use __dockutil__ to add the installed software to the Dock.
# App-update
A common requested behavior is to only update an app if it is already installed. These script verifies if the app is already installed before runnning Installomator.
# v. 9.6 : 2022-11-15 : GitHub API call is first, only try alternative if that fails.
# v. 9.5 : 2022-09-21 : change of GitHub download
# v. 9.4 : 2022-09-14 : downloadURL can fall back on GitHub API
# v. 9.3 : 2022-08-29 : Logging changed for current version. Improved installation with looping if it fails, so it can try again. Improved GitHub handling.
# v. 9.2.2 : 2022-06-17 : Check 1.1.1.1 for internet connection.
# v. 9.2 : 2022-05-19 : Built in installer for Installlomator. Universal script.
# v. 9.6 : 2022-11-15 : GitHub API call is first, only try alternative if that fails.
# v. 9.5 : 2022-09-21 : change of GitHub download
# v. 9.4 : 2022-09-14 : downloadURL can fall back on GitHub API.
# v. 9.3 : 2022-08-29 : Logging changed for current version. Improved installation with looping if it fails, so it can try again. Improved GitHub handling.
# v. 9.2.2 : 2022-06-17 : Check 1.1.1.1 for internet connection.
# v. 9.2 : 2022-05-19 : Built in installer for Installlomator. Universal script.
This script is in the “we find it useful, it is working for us” stage.
Your production and deployment environment will be different, please test thoroughly before rolling it out to your production.
I have put a lot of work into making it stable and safe, but I cannot - of course - make _any_ promises that it won't break in some not yet encountered edge case.
We have put a lot of work into making it stable and safe, but we cannot - of course - make _any_ promises that it won't break in some not yet encountered edge case.
## Authors
Intallomator was originally inspired by the download scripts from William Smith and Sander Schram, and created by:
__Please note, that if you are contributing to this project with new labels or other suggestions in PRs, please put your changes in the fragmented files, not the full `Installomator.sh` script. The full script is now a build of the fragments, and will be overwritten. See the REAMDME.md file in the `utils` directory for detailed instructions.__
__Please note, that if you are contributing to this project with new labels or other suggestions in PRs, please put your changes in the files below `fragments`-folder. DO NOT edit the full `Installomator.sh` script. The full script is now a build of the fragments, and will be overwritten. See the [README.md](utils/README.md) file in the `utils` directory for detailed instructions.__
Discussion, support and advice around Installomator happens in the `#installomator` channel in the [MacAdmins.org Slack](https://macadmins.org). Go there for support questions.
Do not create an issue just when you have a questions, but do file an issue or pull request for bugs or wrong behavior. When in doubt, ask in the above Slack channel.
Do not create an issue just when you have a questions, but do file an issue or pull request (PR) for bugs or wrong behavior. When in doubt, ask in the above Slack channel.
If you have added a new label, then please file a pull request. (and Thank you!)
We try to keep the script as short as possible, and with more than 300 labels, we can save 300 lines in the script, if we do not have credit lines on each of these. So we are thankful for your contribution, but we will be removing these lines in the coming releases.
Please see [CONTRIBUTING.md](https://github.com/Installomator/Installomator/blob/dev/CONTRIBUTING.md) for how to contribute.
## More reading
There are a few interesting post on Installomator on my weblog:
- [Using Installomator with Jamf Pro](https://scriptingosx.com/2020/06/using-installomator-with-jamf-pro/) by Mischa van der Bent
- [Using another MDM than Jamf and you might want a local installation](https://github.com/Theile/Installomator/) By Søren Theilgaard
## Background
As a system engineer at [an Apple Authorized Enterprise Reseller](https://prowarehouse.nl), we manage a lot of Jamf instances.
In the world of managing Apple Macs, organizations can have two different approaches to the management. Either the IT department will tightly manage and verify each piece of software, or they will just want the latest software to be deployed as fast as possible.
Some of these instances are tightly managed, i.e. the versions of the operating system and third party software are controlled and updates will only be pushed with the management system when the administration and security team went through an approval process and then the update is automated. This is an important and valid workflow and the right fit for many deployments.
OK, maybe some software should be tightly managed and others not, but you get the point.
### Tightly managed
If your solution needs to be tightly managed, i.e. the versions of the operating system and third party software are controlled and updates will only be pushed with the management system when the administration and security team went through an approval process and then the update is automated. This is an important and valid workflow and the right fit for many deployments.
Installomator was _not_ written for these kinds of deployment.
If you are running this kind of deployment, you want to use [AutoPkg](https://github.com/autopkg/autopkg) and you can stop reading here.
There are other kinds of deployments, though. In these deployments the management system is merely used to "get the user ready" as quickly as possible when they set up a new machine, and to offer software from a self service portal. In these deployments, system and software installations are 'latest version available' and updates are user driven (though we do want to nag them).
### Latest version always
These deployments are
There are other kinds of deployments, though. In these deployments the management system is merely used to “get the user ready” as quickly as possible when they set up a new machine, and to offer software from a self service portal. In these deployments, system and software installations are ‘latest version available’ and updates are user driven (though we do want to nag them and push them).
Installomator can help with this.
These deployments can be
- user driven
- low control
- minimal maintenance effort
- latest version is best
These are mostly 'user controlled' Macs and we (the admins) just want to assist the user in doing the right thing. And the right thing is (often) to install the latest versions and updates when they are available.
These can be 'user controlled' Macs and we (the admins) just want to assist the user in doing the right thing. And the right thing is (often) to install the latest versions and updates when they are available.
The Mac App Store and software pushed through the Mac App Store follow this approach. When you manage and deploy software through the App Store — whether it is on iOS or macOS — neither the MacAdmin nor the user get a choice of the application version. They will get the latest version.
@@ -65,16 +91,25 @@ Some of these disadvantages can be seen as advantages in different setups. When
Because this is an attractive solution for _certain kinds_ of deployment, there are already many scripts out there that will download and install the latest version of a given software. And we have built and used quite a few in-house, as well. Most importantly, [William Smith has this script](https://gist.github.com/talkingmoose/a16ca849416ce5ce89316bacd75fc91a) which can be used to install several different Microsoft applications and bundles, because Microsoft has a nice unified URL scheme.
At some point, earlier this year, I got frustrated at the number of scripts we were maintaining (or failing to). Also, my concern that most of the scripts weren't doing _any_ verification of the download was getting unbearable. So, I set out to write the one install script to rule them all...
At some point, in 2018, Armin got frustrated at the number of scripts he was maintaining (or failing to). Also, his concern that most of the scripts weren’t doing _any_ verification of the download was getting unbearable. So, he set out to write _the one install script to rule them all…_
### Locally installed
So Armin made the version for Jamf Pro but universally for any MDM to adopt.
Søren looked at this, and wanted this approach to work in Mosyle and Addigy, and for these solutions we need Installomator to be locally installed on the Mac, and then the MDM can call this script from their scripts features. For some time Søren had a version of Installomator that was supplied with a notarized pkg, so it could be deployed as part of DEP or however was needed.
This has now been merged into Installomator, and with contributions of Isaac and Adam, new features and labels have been added more frequently.
## Goals
My goals for Installomator are:
The goals for Installomator are:
- work with various common archive types
- verify the downloaded archive or application
- have a simple 'interface' to the admin
- single script file so it can 'easily' be copied into a management system
- have a simple ‘interface’ to the admin
- single script file so it can ‘easily’ be copied into a management system
- signed and notarized pkg-installer for local installation
- extensible without deep scripting knowledge
- work independently of a specific management system
- no dependencies that may be removed from macOS in the future or are not pre-installed
@@ -91,9 +126,9 @@ Installomator can work with the following common archive and installer types:
When the download yields a pkg file, Installomator will run `installer` to install it on the current system.
Applications in dmgs or zips will be copied to `/Applications` and their owner will be set to the current user, so the install works like a standard drag'n drop installation.
Applications in dmgs or zips will be copied to `/Applications` and their owner will be set to the current user, so the install works like a standard drag'n drop installation. Owner can also be set to root/wheel.
(I consider it a disgrace, that Jamf, after nearly 20 years, _still_ cannot deal with 'drag'n drop installation dmgs' natively. It's not _that_ hard.)
(I consider it a disgrace, that Jamf, after nearly 20 years, _still_ cannot deal with ‘drag’n drop installation dmgs natively. It’s not _that_ hard.)
### Verify the download
@@ -110,11 +145,11 @@ When used to install software, Installomator has a single argument: the label or
There is a debug mode and one other setting that can be controlled with variables in the code. This simplifies the actual use of the script from within a management system.
There is a debug mode and other settings that can be controlled with variables in the code. This simplifies the actual use of the script from within a management system.
### Extensible
As of this writing, Installomator knows how to download and install more than 238 different applications. You can add more by adding a block to the _long_`case` statement starting on line 758. Some of them are more elaborate, but most of them (just) need this information (not really "just" in this case, as we have to differentiate between arm64 and i386 versions for both `downloadURL` and `appNewVersion`):
As of this writing, Installomator knows how to download and install more than 364 different applications. You can add more by adding new labels to the `fragments`-folder. Below is an example of a label, and most of them (just) needs this information (not really "just" in this case, as we have to differentiate between arm64 and i386 versions for both `downloadURL` and `appNewVersion`):
When you know how to extract these pieces of information from the application and/or download, then you can add an application to Installomator.
The script `buildCaseStatement.sh` can help with the label creation.
The script `buildLabel.sh` can help with the label creation. Just server the URL to the script, and it will try to figure out things and write out a label as output. See [Wiki Tutorials](https://github.com/Installomator/Installomator/wiki#tutorials).
Please note: Labels should be named in small caps, numbers 0-9, “-”, and “_”. No other characters allowed.
Actually labels are part of a case-statement, and must be formatted accordingly.
### Not specific to a management system
I wrote this script mainly for use with Jamf Pro, because that is what we use. For testing, you can run the script interactively from the command line. However, I have tried to keep anything that is specific to Jamf optional, or so flexible that it will work anywhere. Even if it does not work with your management system 'out of the box,' the adaptations should be straightforward.
Armin wrote this script mainly for use with Jamf Pro, because that is what he used. For testing, you can run the script interactively from the command line. However, we have tried to keep anything that is specific to Jamf optional, or so flexible that it will work anywhere. Even if it does not work with your management system ‘out of the box’, the adaptations should be straightforward.
Not all MDMs can include the full script, for those MDMs it might be more useful to install it on the client machines, and run it from there. See [Using another MDM than Jamf and you might want a local installation](https://github.com/Theile/Installomator/) By Søren Theilgaard.
Not all MDMs can include the full script, for those MDMs it might be more useful to install it on the client machines, and run it from there. So a PKG to be installed on client Macs is also provided here.
### No dependencies
The script started out as a pure `sh` script, and when I needed arrays I 'switched' to `zsh`, because that is what [we can rely on being in macOS for the foreseeable future](https://scriptingosx.com/zsh). There are quite a few places where using python would have been easier and safer, but with the python 2 run-time being deprecated, that would have added a requirement for a Python 3 run-time to be installed. XML and JSON parsing would have been better with a tool like [scout](https://github.com/ABridoux/scout) or [jq](https://stedolan.github.io/jq/), but those would again require additional installations on the client before the script can run.
The script started out as a pure `sh` script, and when arrays was needed it was ‘switched’ to `zsh`, because that is what [we can rely on being in macOS for the foreseeable future](https://scriptingosx.com/zsh). There are quite a few places where using python would have been easier and safer, but with the python 2 run-time being deprecated, that would have added a requirement for a Python 3 run-time to be installed. XML and JSON parsing would have been better with a tool like [scout](https://github.com/ABridoux/scout) or [jq](https://stedolan.github.io/jq/), but those would again require additional installations on the client before the script can run.
Keeping the script as a `zsh` allows you to paste it into your management system's interface (and disable the DEBUG mode) and use it without requiring any other installations.
@@ -180,19 +217,19 @@ Other than the version arguments, the argument can be any of the labels listed i
### Debug mode
There is a variable named `DEBUG` which is set in line 21 of the script. When `DEBUG` is set to `1` (default) no actions that would actually modify the current system are taken. This is useful for testing most of the actions in the script, but obviously not all of them.
There is a variable named `DEBUG` which is set in line 21 of the script. When `DEBUG` is set to `1` (default) or `2` for a variation of debug, no actions that would actually modify the current system are taken. This is useful for testing most of the actions in the script, but obviously not all of them.
Also when the `DEBUG` variable is `1`, downloaded archives and extracted files will be written to the script's directory, rather than a temporary directory, which can make debugging easier.
When the `DEBUG` variable is `1`, downloaded archives and extracted files will be written to the script's directory, rather than a temporary directory, which can make debugging easier.
_Always remember_ to change the `DEBUG` variable to `0` when deploying.
When `DEBUG` variable is `2`, the temporary folder is created and downloaded and extracted files goes to that folder, as if not in DEBUG mode, but installation is still not done. On the other hand blocking processes are checked, the app is reopened if closed, and the user is notified.
### Use Installomator with Jamf Pro
Debug mode 1 is useful to test the download and verification process without having to re-download and re-install an application or package on your system. Debug mode 2 is great for checking running processe and notifications.
In Jamf Pro, create a new 'Script' and paste the contents of `Installomator.sh` into the 'Script Contents' area. Under 'Options' you can change the parameter label for argument 4 to 'Application Label.'
_Always remember_ to change the `DEBUG` variable to `0` when deploying. The installer PKG we provide has `DEBUG=0`.
Remember to set `DEBUG` to `0`.
### Use Installomator with various MDM solutions
Then you can use the Installomator script in a policy and choose the application to install by setting the label for argument 4.
In the wiki we have provided documentation on how Installomator is used in various MDM solution, like [Jamf Pro](https://github.com/Installomator/Installomator/wiki/MDM:-Jamf-Pro), [Mosyle](https://github.com/Installomator/Installomator/wiki/MDM:-Mosyle-(Business,-Fuse,-and-Manager)), and [Addigy](https://github.com/Installomator/Installomator/wiki/MDM:-Addigy).
## What it does
@@ -200,7 +237,7 @@ When it runs with a known label, the script will perform the following:
- Check the version installed with the version online. Only continue if it's different
- download the latest version from the vendor
- when the application is running, prompt the user to quit or cancel
- when the application is running, prompt the user to quit or cancel (customizable)
- dmg or zip archives:
- extract the application and copy it to /Applications
- change the owner of the application to the current user
@@ -208,19 +245,11 @@ When it runs with a known label, the script will perform the following:
- when necessary, extract the pkg from the enclosing archive
- install the pkg with the `installer` tool
- clean up the downloaded files
- notify the user
- notify the user (also customizable)
## Configuring the script
As of now there are two settings that are meant to configured when deploying the script.
### Debug mode
The first is the `DEBUG` variable. When this is set to `1` the script will _not_ perform any changes to the current system. In other words, no application will be copied to the target directory and no `installer` command be performed.
In addition, files will be downloaded and extracted to the Installomator project folder instead of a temporary directory and _not_ deleted when the script exits. Also archives will _not_ be re-downloaded when they already exist in the project folder. The repository's `.gitignore` file is set up to ignore the archive file extensions.
Debug mode is useful to test the download and verification process without having to re-download and re-install an application or package on your system.
We have several default settings for certain behavior and notifications inside the script, but these can be customized when calling the script.
### Blocking Process actions
@@ -229,13 +258,13 @@ The `BLOCKING_PROCESS_ACTION` variable controls the behavior of the script when
There are eight options:
-`ignore`: continue even when blocking processes are found.
-`silent_fail`: exit script without prompt or installation.
-`prompt_user`: (default) show a user dialog for each blocking process found abort after three attempts to quit (only if user accepts to quit the apps, otherwise the update is cancelled).
-`prompt_user_then_kill`: show a user dialog for each blocking process found, attempt to quit two times, kill the process finally.
-`silent_fail`: Exit script without prompt or installation.
-`prompt_user`: Show a user dialog for each blocking process found, user can choose "Quit and Update" or "Not Now". When "Quit and Update" is chosen, blocking process will be told to quit. Installomator will wait 30 seconds before checking again in case Save dialogs etc are being responded to. Installomator will abort if quitting after three tries does not succeed. "Not Now" will exit Installomator.
-`prompt_user_then_kill`: show a user dialog for each blocking process found, user can choose "Quit and Update" or "Not Now". When "Quit and Update" is chosen, blocking process will be terminated. Installomator will abort if terminating after two tries does not succeed. "Not Now" will exit Installomator.
-`prompt_user_loop`: Like prompt-user, but clicking "Not Now", will just wait an hour, and then it will ask again.
WARNING! It might block the MDM agent on the machine, as the scripts gets stuct in waiting until the hour has passed, possibly blocking for other management actions in this time.
-`tell_user`: User will be showed a notification about the important update, but user is only allowed to quit and continue, and then we ask the app to quit.
-`tell_user_then_kill`: Show dialog 2 times, and if the quitting fails, the blocking processes will be killed.
WARNING! It might block the MDM agent on the machine, as the script will not exit, it will pause until the hour has passed, possibly blocking for other management actions in this time.
-`tell_user`: (Default) User will be showed a notification about the important update, but user is only allowed to Quit and Continue, and then we ask the app to quit. This is default.
-`tell_user_then_kill`: User will be showed a notification about the important update, but user is only allowed to Quit and Continue. If the quitting fails, the blocking processes will be terminated.
-`kill`: kill process without prompting or giving the user a chance to save.
If any process was closed, Installomator will try to open the app again, after the update process is done.
@@ -265,11 +294,17 @@ __options:__
-`no`: If installed app is from App Store (which include VPP installed apps) it will not be touched, no matter it's version (default)
-`yes`: Replace App Store (and VPP) version of app and handle future updates using Installomator, even if latest version. Shouldn’t give any problems for the user in most cases. Known bad example: Slack will loose all settings.
### Owner of copied apps
Default is `SYSTEMOWNER=0`
__options:__
-`0`: Current user will be owner of copied apps, just like if they installed it themselves (default).
-`1`: root:wheel will be set on the copied app. Useful for shared machines.
### Install behavior (force installation)
Since we now make a version checking, and only installs the software if the version is different, an `INSTALL` variable can be used to force the installation:
-``: When not set, software is only installed if it is newer/different in version (default)
-` `: When not set, software is only installed if it is newer/different in version (default)
-`force`: Install even if it’s the same version
### Re-opening of closed app
@@ -279,9 +314,29 @@ The `REOPEN` can be used to prevent the reopening of a closed app
-`yes`: (default) app will be reopened if it was closed
-`no`: app not reopened
### Adding applications/label blocks
### Configuration from Arguments
#### Required Variables
You can provide a configuration variable, such as `DEBUG` or `NOTIFY` as an argument in the form `VAR=value`. For example:
Providing variables this way will override any variables set in the script.
You can even provide _all_ the variables necessary for download and installation. Of course, without a label the argument parsing will fail, so I created a special label `valuesfromarguments` which only checks if the four required values are present:
The order of the variables and label is not relevant. But, when you provide more than one label, all but the _last_ label will be ignored.
Providing all the variables this way might be useful for certain downloads that have a customized URL for each vendor/customer (like customized TeamView or Watchman Monitoring) or are local downloads.
## Adding applications/label blocks
### Required Variables
The script requires four pieces of information to download and install an application:
@@ -314,6 +369,12 @@ The URL from which to download the archive.
The URL can be generated by a series of commands, for example when you need to parse an xml file for the latest URL. (See `bbedit`, `desktoppr`, or `omnigraffle` for examples.)
Sometimes version differs between Intel and Apple Silicon versions. (See `brave`, `obsidian`, `omnidisksweeper`, or `notion`).
-`curlOptions`: (array, optional)
Options to the `curl` command, needed for `curl` to be able to download the software.
Usually used for adding extra headers that some servers need in order to serve the file.
`curlOptions=( -H "User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.1 Safari/605.1.15" )`
(See “mocha”-labels, for examples on labels, and `buildLabel.sh` for header-examples.)
-`appNewVersion` (optional, but recommended):
Version of the downloaded software.
If given, it will be compared to installed version, to see if download is different.
@@ -334,8 +395,7 @@ The 10-character Developer Team ID with which the application or pkg is signed a
- Installation Packages (pkg)
`spctl -a -vv -t install ~/Downloads/desktoppr-0.2.pkg`
#### Optional Variables
### Optional Variables
Depending on the application or pkg there are a few more variables you can or need to set. Many of these are derived from the required variables, but may need to be set manually if those derived values do not work.
@@ -374,47 +434,35 @@ Depending on the application or pkg there are a few more variables you can or ne
`$updateTool $updateArguments`
Will be run instead of of downloading and installing a complete new version.
Use this when the `updateTool` does differential and optimized downloads.
e.g. `msupdate` (see microsoft installations)
e.g. `msupdate` (see various Microsoft installations).
-`updateToolRunAsCurrentUser`:
When this variable is set (any value), `$updateTool` will be run as the current user. Default is unset and
### Configuration from Arguments
You can provide a configuration variable, such as `DEBUG` or `NOTIFY` as an argument in the form `VAR=value`. For example:
Providing variables this way will override any variables set in the script.
You can even provide _all_ the variables necessary for download and installation. Of course, without a label the argument parsing will fail, so I created a special label `valuesfromarguments` which only checks if the four required values are present:
The order of the variables and label is not relevant. But, when you provide more than one label, all but the _last_ label will be ignored.
Providing all the variables this way might be useful for certain downloads that have a customized URL for each vendor/customer (like customized TeamView or Watchman Monitoring) or are local downloads.
-`CLIInstaller`:
-`CLIArguments`:
If the downloaded dmg is actually an installer that we can call using CLI, we can use these two variables for what to call.
We need to define `name` for the installed app (to be version checked), as well as `installerTool` for the installer app (if named differently that `name`. Installomator will add the path to the folder/disk image with the binary, and it will be called like this:
`$CLIInstaller $CLIArguments`
For most installations `CLIInstaller` should contain the `installerTool` for the CLI call (if it’s the same).
We can support a whole range of other software titles by implementing this.
See label adobecreativeclouddesktop.
-`installerTool`:
Introduced as part of `CLIInstaller`. If the installer in the DMG or ZIP is named differently than the installed app, then this variable can be used to name the installer that should be located after mounting/expanding the downloaded archive.
See label adobecreativeclouddesktop
## Frequently Asked Questions
### What if the latest version of the app is already installed?
Short answer: Installomator will re-download and re-install the latest over the existing installation.
Short answer: That depends on if labels will know what the latest version will be.
Longer answer:
Installomator will try to find a currently installed app to log the version. When Installomator finds an existing app (any version) and the `updateTool` variable is set, then Installomator will _not_ download and install, but run the `updateTool` instead.
However, there is no simple generic method to actually determine the latest version of an application or installer.
We deploy Installomator usually for user initiated installations from Self Service, so re-installs don't really 'hurt' and may be a useful troubleshooting step.
When you want to have automated installations, you can use smart groups based on the app version to limit excessive re-installations.
- Labels without this will re-download and re-install the latest over the existing installation.
- Labels with this info will only install the app if the version is different than the one installed.
- Labels that can use update tool will use that for the update (if the version is different)
### Why don't you just use `autopkg install`?
@@ -444,7 +492,7 @@ Please don't misunderstand this as me saying that AutoPkg is a bad or poorly des
But it is not suited as a client install automation tool.
### Why don't you just use brew?
### Why don't you just use brew or MacPorts?
Read the explanation for `autopkg`, pretty much the same applies for `brew`, i.e. while it is useful on a single Mac, it is a un-manageable mess when you think about deploying and managing on a fleet of computers.
# if an argument contains an = character, send it to eval
printlog "setting variable from argument $1"
printlog "setting variable from argument $1" INFO
eval$1
else
# assume it's a label
@@ -36,44 +38,100 @@ done
# lowercase the label
label=${label:l}
printlog "################## Start Installomator v. $VERSION"
printlog "################## $label"
# separate check for 'version' in order to print plain version number without any other information
if[[$label=="version"]];then
echo"$VERSION"
exit0
fi
# MARK: Logging
log_location="/private/var/log/Installomator.log"
# Check if we're in debug mode, if so then set logging to DEBUG, otherwise default to INFO
# if no log level is specified.
if[[$DEBUG -ne 0]];then
LOGGING=DEBUG
elif[[ -z $LOGGING]];then
LOGGING=INFO
datadogLoggingLevel=INFO
fi
# Associate logging levels with a numerical value so that we are able to identify what
# should be removed. For example if the LOGGING=ERROR only printlog statements with the
# level REQ and ERROR will be displayed. LOGGING=DEBUG will show all printlog statements.
# If a printlog statement has no level set it's automatically assigned INFO.
declare -A levels=(DEBUG 0 INFO 1 WARN 2 ERROR 3 REQ 4)
# If we are able to detect an MDM URL (Jamf Pro) or another identifier for a customer/instance we grab it here, this is useful if we're centrally logging multiple MDM instances.
# while debugging, items will be downloaded to the parent directory of this script
# also no actual installation will be performed
# debug mode 1 will download to the directory the script is run in, but will not check the version
# debug mode 2 will download to the temp directory, check for blocking processes, check the version, but will not install anything or remove the current version
DEBUG=1
# notify behavior
@@ -32,34 +34,40 @@ NOTIFY=success
# - silent no notifications
# - all all notifications (great for Self Service installation)
# behavior when blocking processes are found
BLOCKING_PROCESS_ACTION=tell_user
# options:
# - ignore continue even when blocking processes are found
# - quit app will be told to quit nicely, if running
# - quit app will be told to quit nicely if running
# - quit_kill told to quit twice, then it will be killed
# Could be great for service apps, if they do not respawn
# Could be great for service apps if they do not respawn
# - silent_fail exit script without prompt or installation
# - prompt_user show a user dialog for each blocking process found
# abort after three attempts to quit
# (only if user accepts to quit the apps, otherwise
# the update is cancelled).
# - prompt_user show a user dialog for each blocking process found,
# user can choose "Quit and Update" or "Not Now".
# When "Quit and Update" is chosen, blocking process
# will be told to quit. Installomator will wait 30 seconds
# before checking again in case Save dialogs etc are being responded to.
# Installomator will abort if quitting after three tries does not succeed.
# "Not Now" will exit Installomator.
# - prompt_user_then_kill
# show a user dialog for each blocking process found,
# attempt to quit two times, kill the process finally
# user can choose "Quit and Update" or "Not Now".
# When "Quit and Update" is chosen, blocking process
# will be terminated. Installomator will abort if terminating
# after two tries does not succeed. "Not Now" will exit Installomator.
# - prompt_user_loop
# Like prompt-user, but clicking "Not Now", will just wait an hour,
# and then it will ask again.
# WARNING! It might block the MDM agent on the machine, as
# the scripts gets stuct in waiting until the hour has passed,
# the script will not exit, it will pause until the hour has passed,
# possibly blocking for other management actions in this time.
# - tell_user User will be showed a notification about the important update,
# but user is only allowed to quit and continue, and then we
# ask the app to quit.
# but user is only allowed to Quit and Continue, and then we
# ask the app to quit. This is default.
# - tell_user_then_kill
# Show dialog 2 times, and if the quitting fails, the
# blocking processes will be killed.
# User will be showed a notification about the important update,
# but user is only allowed to Quit and Continue. If the quitting fails,
# the blocking processes will be terminated.
# - kill kill process without prompting or giving the user a chance to save
@@ -71,6 +79,8 @@ LOGO=appstore
# - mosyleb Mosyle Business
# - mosylem Mosyle Manager (Education)
# - addigy Addigy
# - microsoft Microsoft Endpoint Manager (Intune)
# - ws1 Workspace ONE (AirWatch)
# path can also be set in the command call, and if file exists, it will be used.
# Like 'LOGO="/System/Applications/App\ Store.app/Contents/Resources/AppIcon.icns"'
# (spaces have to be escaped).
@@ -79,18 +89,25 @@ LOGO=appstore
# App Store apps handling
IGNORE_APP_STORE_APPS=no
# options:
# - no If installed app is from App Store (which include VPP installed apps)
# it will not be touched, no matter it's version (default)
# - yes Replace App Store (and VPP) version of app and handle future
# - no If the installed app is from App Store (which include VPP installed apps)
# it will not be touched, no matter its version (default)
# - yes Replace App Store (and VPP) version of the app and handle future
# updates using Installomator, even if latest version.
# Shouldn’t give any problems for the user in most cases.
# Known bad example: Slack will loose all settings.
# Known bad example: Slack will lose all settings.
# Owner of copied apps
SYSTEMOWNER=0
# options:
# - 0 Current user will be owner of copied apps, just like if they
# installed it themselves (default).
# - 1 root:wheel will be set on the copied app.
# Useful for shared machines.
# install behavior
INSTALL=""
# options:
# - When not set, software will only be installed
# - When not set, the software will only be installed
# if it is newer/different in version
# - force Install even if it’s the same version
@@ -98,9 +115,49 @@ INSTALL=""
# Re-opening of closed app
REOPEN="yes"
# options:
# - yes App wil be reopened if it was closed
# - yes App will be reopened if it was closed
# - no App not reopened
# Only let Installomator return the name of the label
# RETURN_LABEL_NAME=0
# options:
# - 1 Installomator will return the name of the label and exit, so last line of
# output will be that name. When Installomator is locally installed and we
# use DEPNotify, then DEPNotify can present a more nice name to the user,
# instead of just the label name.
# Interrupt Do Not Disturb (DND) full screen apps
INTERRUPT_DND="yes"
# options:
# - yes Script will run without checking for DND full screen apps.
# - no Script will exit when an active DND full screen app is detected.
# Comma separated list of app names to ignore when evaluating DND
IGNORE_DND_APPS=""
# example that will ignore browsers when evaluating DND:
# These variables will allow Installomator to communicate progress with Swift Dialog
# https://github.com/bartreardon/swiftDialog
# This requires Swift Dialog 2.11.2 or higher.
DIALOG_CMD_FILE=""
# When this variable is set, Installomator will write Swift Dialog commands to this path.
# Installomator will not launch Swift Dialog. The process calling Installomator will have
# launch and configure Swift Dialog to listen to this file.
# See `MDM/swiftdialog_example.sh` for an example.
DIALOG_LIST_ITEM_NAME=""
# When this variable is set, progress for downloads and installs will be sent to this
# listitem.
# When the variable is unset, progress will be sent to Swift Dialog's main progress bar.
# NOTE: How labels work
@@ -124,7 +181,7 @@ REOPEN="yes"
#
# - packageID: (optional)
# The package ID of a pkg
# If given, will be used to find version of installed software, instead of searching for an app.
# If given, will be used to find the version of installed software, instead of searching for an app.
# Usefull if a pkg does not install an app.
# See label installomator_st
#
@@ -132,16 +189,22 @@ REOPEN="yes"
# URL to download the dmg.
# Can be generated with a series of commands (see BBEdit for an example).
#
# - curlOptions: (array, optional)
# Options to the curl command, needed for curl to be able to download the software.
# Usually used for adding extra headers that some servers need in order to serve the file.
# curlOptions=( -H "User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.1 Safari/605.1.15" )
# (See “mocha”-labels, for examples on labels, and buildLabel.sh for header-examples.)
#
# - appNewVersion: (optional)
# Version of the downloaded software.
# If given, it will be compared to installed version, to see if download is different.
# If given, it will be compared to the installed version, to see if the download is different.
# It does not check for newer or not, only different.
#
# - versionKey: (optional)
# How we get version number from app. Possible values:
# - CFBundleShortVersionString
# - CFBundleVersion
# Not all software titles uses fields the same.
# Not all software titles uses fields the same.
# See Opera label.
#
# - appCustomVersion(){}: (optional function)
@@ -164,6 +227,8 @@ REOPEN="yes"
# - archiveName: (optional)
# The name of the downloaded file.
# When not given the archiveName is derived from the $name.
# Note: This has to be defined BEFORE calling downloadURLFromGit or
# versionFromGit functions in the label.
#
# - appName: (optional)
# File name of the app bundle in the dmg to verify and copy (include .app).
@@ -186,18 +251,74 @@ REOPEN="yes"
# blockingProcesses=( NONE )
#
# - pkgName: (optional, only used for pkgInDmg, dmgInZip, and appInDmgInZip)
# File name of the pkg/dmg file _inside_ the dmg or zip
# File name or path to the pkg/dmg file _inside_ the dmg or zip.
# When not given the pkgName is derived from the $name
#
# - updateTool:
# - updateToolArguments:
# When Installomator detects an existing installation of the application,
# and the updateTool variable is set
# $updateTool $updateArguments
# $updateTool $updateArguments
# Will be run instead of of downloading and installing a complete new version.
# Use this when the updateTool does differential and optimized downloads.
# e.g. msupdate
# e.g. msupdate on various Microsoft labels
#
# - updateToolRunAsCurrentUser:
# When this variable is set (any value), $updateTool will be run as the current user.
#
# - CLIInstaller:
# - CLIArguments:
# If the downloaded dmg is an installer that we can call using CLI, we can
# use these two variables for what to call.
# We need to define `name` for the installed app (to be version checked), as well as
# `installerTool` for the installer app (if named differently than `name`. Installomator
# will add the path to the folder/disk image with the binary, and it will be called like this:
# $CLIInstaller $CLIArguments
# For most installations `CLIInstaller` should contain the `installerTool` for the CLI call
# (if it’s the same).
# We can support a whole range of other software titles by implementing this.
# See label adobecreativeclouddesktop
#
# - installerTool:
# Introduced as part of `CLIInstaller`. If the installer in the DMG or ZIP is named
# differently than the installed app, then this variable can be used to name the
# installer that should be located after mounting/expanding the downloaded archive.
# See label adobecreativeclouddesktop
#
### Logging
# Logging behavior
LOGGING="INFO"
# options:
# - DEBUG Everything is logged
# - INFO (default) normal logging level
# - WARN only warning
# - ERROR only errors
# - REQ ????
# MDM profile name
MDMProfileName=""
# options:
# - MDM Profile Addigy has this name on the profile
# - Mosyle Corporation MDM Mosyle uses this name on the profile
# From the LOGO variable we can know if Addigy og Mosyle is used, so if that variable
# is either of these, and this variable is empty, then we will auto detect this.
# Datadog logging used
datadogAPI=""
# Simply add your own API key for this in order to have logs sent to Datadog
# See more here: https://www.datadoghq.com/product/log-management/
# Log Date format used when parsing logs for debugging, this is the default used by
# install.log, override this in the case statements if you need something custom per
# application (See adobeillustrator). Using stadard GNU Date formatting.
LogDateFormat="%Y-%m-%d %H:%M:%S"
# Get the start time for parsing install.log if we fail.
localhttpstatus=$(curl -X HEAD -s "https://ardownload2.adobe.com/pub/adobe/reader/mac/AcrobatDC/${version}/AcroRdrDC_${version}_MUI.dmg" --write-out "%{http_code}")
printlog "HTTP status for Adobe Reader full installer URL https://ardownload2.adobe.com/pub/adobe/reader/mac/AcrobatDC/${version}/AcroRdrDC_${version}_MUI.dmg is $httpstatus" DEBUG
downloadURL=$(redirect=$(curl -sfL https://www.blender.org/download/ | sed 's/.*href="//'| sed 's/".*//'| grep .dmg)&& curl -sfL "$redirect"| sed 's/.*href="//'| sed 's/".*//'| grep -m1 .dmg)
if[[$(arch)=="arm64"]];then
downloadURL=$(curl -sfL "https://www.blender.org/download/"| xmllint --html --format - 2>/dev/null | grep -o "https://.*blender.*arm64.*.dmg"| sed '2p;d'| sed 's/www.blender.org\/download/download.blender.org/g')
elif[[$(arch)=="i386"]];then
downloadURL=$(curl -sfL "https://www.blender.org/download/"| xmllint --html --format - 2>/dev/null | grep -o "https://.*blender.*x64.*.dmg"| sed '2p;d'| sed 's/www.blender.org\/download/download.blender.org/g')
fi
appNewVersion=$(echo"${downloadURL}"| sed -E 's/.*\/[a-zA-Z]*-([0-9.]*)-.*/\1/g')
downloadURL=$(curl -H "User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.1 Safari/605.1.15" -fs "https://support.techsmith.com/hc/en-us/articles/360004908652-Desktop-Product-Download-Links"| grep -A 3"Camtasia (Mac) 2021"| sed 's/.*href="//'| sed 's/".*//'| grep .dmg)
appNewVersion=$(curl -H "User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.1 Safari/605.1.15" -fs "https://support.techsmith.com/hc/en-us/articles/360004908652-Desktop-Product-Download-Links"| grep "Camtasia (Mac) 2021"| sed -e 's/.*Camtasia (Mac) //' -e 's/<\/td>.*//')
downloadURL=$(curl -H "User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.1 Safari/605.1.15" -fs "https://support.techsmith.com/hc/en-us/articles/360004908652-Desktop-Product-Download-Links"| grep -A 3"Camtasia (Mac) 2019"| sed 's/.*href="//'| sed 's/".*//'| grep .dmg)
appNewVersion=$(curl -H "User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.1 Safari/605.1.15" -fs "https://support.techsmith.com/hc/en-us/articles/360004908652-Desktop-Product-Download-Links"| grep "Camtasia (Mac) 2019"| sed -e 's/.*Camtasia (Mac) //' -e 's/<\/td>.*//')
downloadURL=$(curl -H "User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.1 Safari/605.1.15" -fs "https://support.techsmith.com/hc/en-us/articles/360004908652-Desktop-Product-Download-Links"| grep -A 3"Camtasia (Mac) 2020"| sed 's/.*href="//'| sed 's/".*//'| grep .dmg)
appNewVersion=$(curl -H "User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.1 Safari/605.1.15" -fs "https://support.techsmith.com/hc/en-us/articles/360004908652-Desktop-Product-Download-Links"| grep "Camtasia (Mac) 2020"| sed -e 's/.*Camtasia (Mac) //' -e 's/<\/td>.*//')
appNewVersion="$(eval"$(echo$downloadURL| sed -E 's/.*(MajorVersion.*BuildVersion=[0-9]*).*/\1/'| sed 's/&//g')";((MajorVersion++)) ; ((MajorVersion--)); ((MinorVersion++)) ; ((MinorVersion--)); ((PatchVersion++)) ; ((PatchVersion--)); ((BuildVersion++)) ; ((BuildVersion--)); echo "${MajorVersion}.${MinorVersion}.${PatchVersion}-b${BuildVersion}")"
expectedTeamID="P6CDJZR997"
;;
Some files were not shown because too many files have changed in this diff
Show More
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.