Skip to content

Instantly share code, notes, and snippets.

@anthonyclarka2
Created July 9, 2019 17:09
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save anthonyclarka2/31844e27525380c9a86a2e18a97cd866 to your computer and use it in GitHub Desktop.
Save anthonyclarka2/31844e27525380c9a86a2e18a97cd866 to your computer and use it in GitHub Desktop.
ilikepi 1 hour ago | unvote [-]
It's not to hard to extract the app bundle from the .pkg file. This is how I've always installed it. Do this from an empty directory, though, since it will just spray files everywhere...
* Use `xar` to extract the contents of the .pkg file:
$ xar -xf Zoom.pkg
* Use `cpio` to extract the payload, which is in a file oddly named "Scripts":
$ mkdir payload && cd payload
$ cpio -i -d < ../Scripts
* The app bundle is compressed within a 7z archive, but the .pkg file contains a precompiled decompressor. Either use that or install your own (e.g. via Homebrew) to extract the app bundle:
$ 7zr x zm.7z
Now you will have a directory called "zoom.us.app", which is the app bundle. Move this to wherever you want it to live, and now you've "installed" the app without running the scripts from the .pkg.
Importantly, note that the app will still exhibit the behavior discussed in the article. When you run it the first time, it will install ZoomOpener, which is the helper app that includes the web server. It will not install any browser extensions, however, which is the behavior I was originally trying to avoid by going through this procedure.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment