Carlo Cabrera

> A method for checking if the GCC version that was used to build the other build dependents is new enough to also build `glibc`, and vendor the newer GCC...

> but now that we have to start debottling formulae on Linux we should aim to get something merged that we know works I've bought you some time to get...

> We could be ready to just hard disallow libcrypt.so.1 in all taps from now but we need to actually make that change first and ship that rather than wait...

> I guess this is what I'm struggling with. This case is solving for cases where the user has: > > - too old or missing build tools on their...

If the concern about reusing existing formulae is that they are built against a `glibc` that is too new, use `pour_bottle?` to restrict bottle usage to systems where the bottles...

We should wait for https://github.com/Homebrew/homebrew-core/pull/107517 to merge to avoid introducing a merge conflict there.

We might also want to consider making `libpq` not-keg-only.

Does it crash if you use a JRE that wasn't built by Homebrew? A JRE provided by a Cask is fine.

Needs to be `codesign`ed after doing that. But we really don't need to call `change_dylib`; we can just set `CMAKE_INSTALL_RPATH` instead. ```diff diff --git a/Formula/poppler.rb b/Formula/poppler.rb index e610f7e24ef..a4bb5e5ff4b 100644 ---...

You can use `ENV["FOO"]`, but that environment variable will probably get sanitised by `brew`. Is it meant to be something a user sets?