Simplify MFC deps install: let pip choose wheels vs source builds

Removed --no-binary :all: flag that was forcing ALL packages to compile
from source, which caused failures for Rust-based packages like 'typos'
that require Rust compiler.

New approach:
- Set LDFLAGS with -headerpad_max_install_names in environment
- Let pip decide whether to use wheels or compile from source
- Pip will use LDFLAGS when compiling C extensions (like orjson)
- Most packages will use pre-built wheels (faster, no extra deps needed)
- Only packages that need compilation will be built from source

This is simpler, faster, and avoids requiring Rust/other compilers
while still fixing the bottle relocation issues for packages with
C extensions that need custom header padding.

Author: sbryngelson

packaging/homebrew/mfc.rb

@@ -37,11 +37,10 @@ def install
     ENV.append "LDFLAGS", "-Wl,-headerpad_max_install_names"
 
     # Install MFC Python package and dependencies into venv
-    # Force compilation from source (--no-binary :all:) to ensure our LDFLAGS are applied
-    # Pre-built wheels don't have proper header padding for bottle relocation
-    # Keep toolchain in buildpath for now - mfc.sh needs it there
     # Use editable install (-e) to avoid RECORD file issues when venv is symlinked at runtime
-    system venv/"bin/pip", "install", "--no-binary", ":all:", "-e", buildpath/"toolchain"
+    # Most dependencies use pre-built wheels; only packages with C extensions will be compiled
+    # Keep toolchain in buildpath for now - mfc.sh needs it there
+    system venv/"bin/pip", "install", "-e", buildpath/"toolchain"
 
     # Create symlink so mfc.sh uses our pre-installed venv
     mkdir_p "build"