Working on Brew with CyberArk EPM

[tcapacci]

Output of brew config

thomas@LT-FHWT9GD ~ % brew config
HOMEBREW_VERSION: 4.3.6
ORIGIN: https://github.com/Homebrew/brew.git
HEAD: e8430b25a1d1321f32e5093d62b57b5cb7cfb3c3
Last commit: 5 days ago
Core tap JSON: 21 Jun 08:39 UTC
Core cask tap JSON: 21 Jun 08:39 UTC
HOMEBREW_PREFIX: /Users/thomas/brew
HOMEBREW_REPOSITORY: /Users/thomas/brew
HOMEBREW_CELLAR: /Users/thomas/brew/Cellar
HOMEBREW_CASK_OPTS: []
HOMEBREW_MAKE_JOBS: 14
Homebrew Ruby: 3.3.3 => /Users/thomas/brew/Library/Homebrew/vendor/portable-ruby/3.3.3/bin/ruby
CPU: 14-core 64-bit arm_palma
Clang: 15.0.0 build 1500
Git: 2.39.3 => /Library/Developer/CommandLineTools/usr/bin/git
Curl: 8.6.0 => /usr/bin/curl
macOS: 14.5-arm64
CLT: 15.3.0.0.1.1708646388
Xcode: N/A
Rosetta 2: false

Output of brew doctor

thomas@LT-FHWT9GD ~ % brew doctor
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry or file an issue; just ignore this. Thanks!

Warning: Your Homebrew's prefix is not /opt/homebrew.

Many of Homebrew's bottles (binary packages) can only be used with the default prefix.
Consider uninstalling Homebrew and reinstalling into the default prefix.
It is expected behaviour that some formulae will fail to build in this unsupported configuration.
It is expected behaviour that Homebrew will be buggy and slow.
Do not create any issues about this on Homebrew's GitHub repositories.
Do not create any issues even if you think this message is unrelated.
Any opened issues will be immediately closed without response.
Do not ask for help from Homebrew or its maintainers on social media.
You may ask for help in Homebrew's discussions but are unlikely to receive a response.
Try to figure out the problem yourself and submit a fix as a pull request.
We will review it but may or may not accept it.


### Description of issue

Hi all, We have CyberArk EPM running on our laptops, which is an Endpoint Manager that prevents users from being local admins so we can create policies that they can elevate or sudo as needed by allowing application or command lines.
CyberArk has a KB to install Brew in the user context https://cyberark.my.site.com/s/article/How-to-install-HomeBrew-on-Mac-with-EPM-as-a-User-context

It seems all formula needs to compile all packages using that type of install, so installations take an hour and clog the CPU to 100% CPU. While I am working with CyberArk support, do you know why the packages are compiled and if there is anything we can do to prevent it so packages are installed faster?

Excerpt from logs to install openssl:

==> Pouring ca-certificates--2024-03-11.all.bottle.tar.gz
==> Regenerating CA certificate bundle from keychain, this may take a while...
🍺  /Users/thomas/brew/Cellar/ca-certificates/2024-03-11: 4 files, 232.4KB
==> Installing openssl@3
==> perl ./Configure --prefix=/Users/thomas/brew/Cellar/openssl@3/3.3.1 --openssldir=/Users/thomas/brew/etc/openssl@3 --libdir=lib no-ssl3 no-ssl3-method no-zlib darwin64-arm64-cc enable-ec_nistp_64_gcc_128
==> make

==> make install MANDIR=/Users/thomas/brew/Cellar/openssl@3/3.3.1/share/man MANSUFFIX=ssl
==> make test TESTS=-test_afalg

[SMillerDev]

While I am working with CyberArk support, do you know why the packages are compiled and if there is anything we can do to prevent it so packages are installed faster?

It's this output from brew doctor:

Warning: Your Homebrew's prefix is not /opt/homebrew.

Many of Homebrew's bottles (binary packages) can only be used with the default prefix.
Consider uninstalling Homebrew and reinstalling into the default prefix.
It is expected behaviour that some formulae will fail to build in this unsupported configuration.
It is expected behaviour that Homebrew will be buggy and slow.
Do not create any issues about this on Homebrew's GitHub repositories.
Do not create any issues even if you think this message is unrelated.
Any opened issues will be immediately closed without response.
Do not ask for help from Homebrew or its maintainers on social media.
You may ask for help in Homebrew's discussions but are unlikely to receive a response.
Try to figure out the problem yourself and submit a fix as a pull request.
We will review it but may or may not accept it.

[tcapacci]

Would using --force-bottle prevent packages from being compiled to speed up installs?

[SMillerDev]

Yes, but a lot of them would probably break in ways that are near impossible to debug.