Daniel Nachun

> What's the benefit to building two different kinds of bottles? What determines which kind of bottle a user gets? Great question. Right now, when a user tries to install...

> I overcounted a little (just by about a 50%...): > > ``` > ❯ rg --files-without-match '(cellar: :any)|(bottle :unneeded)' | wc -l > 989 > ``` Wow, that's really...

> @danielnachun Sorry, what I'm proposing is we don't distribute any of these bottles (with the longer prefix) to users until we've verified the approach on our local machines. Feature...

> We can build just the one bottle with prefix `/home/linuxbrew/.linuxbrew` and roll out binary relocation to users whose `brew --prefix` is no more than 26 characters in this order…...

Now that I've gotten `glibc` bootstrapping to working on CentOS 7 (see https://github.com/Homebrew/homebrew-core/pull/106837), we no longer need to worry about portability to even the oldest support versions of Linux for...

> I think it might be worth us allowing `depends_on "gfortran"` to use an alias in this specific case to avoid confusion. This would help to clarify things a lot...

Actually `glibc` only should be updated when the CI image is updated, so it would only get updated every 2 years if we follow the LTS release schedule, making this...

> A system with a single version of Glibc is less complex and easier to administer than a system with multiple versions of Glibc, which is pretty unusual. Can you...

I have an important update on the `glibc` side of things - after a lot of discussion we've arrived on a very robust and simple solution in https://github.com/Homebrew/homebrew-core/pull/106837 that means...

The `glibc` update has shipped. The only other blocker now is https://github.com/Homebrew/brew/pull/13577 and that is almost finished too. One other detail we need to take care of is making sure...