3 ms·

IIRC the main reason here is that brew path is hardcoded during the build process of packages, which means that you wouldn't be able to use bottles. I didn't c

IIRC the main reason here is that brew path is hardcoded during the build process of packages, which means that you wouldn't be able to use bottles. I didn't check, but there is a chance that path is also hardcoded in (some) formulae, so even building from the source might not help here.

scribu 1y ago
You could run the build process with chroot or inside Docker, so that the hardcoded paths actually resolve to a designated subdirectory.
- mananaysiempre 1y ago
  Incidentally, that’s what is usually done in Nixpkgs in similar situations when there’s no better alternative, see buildFHSEnv et al.
- akdev1l 1y ago
  In many cases the build output also has hardcoded paths unfortunately so doing `brew install` inside a container with the proper volumes it’s not sufficient to fix the issue. Everything would have to run from within the container as well.