Carlo Cabrera

Yes, that was my understanding too, and based on my (apparently mistaken) testing, how it worked. Looking at it now, that doesn't seem to be how the code works. I...

Ok, gotcha. Let me give it a try.

It does not work: ``` ❯ brew outdated hello (2.12.1) < 2.12.1 ❯ brew upgrade hello ==> Upgrading 1 outdated package: hello 2.12.1 -> 2.12.1 ==> Downloading https://ghcr.io/v2/homebrew/core/hello/manifests/2.12.1 Already downloaded:...

Yes, mostly. But the removal of this hack https://github.com/Homebrew/brew/blob/4a623e0a2532a00a42474c755b8c03e927594676/Library/Homebrew/extend/os/linux/linkage_checker.rb#L75-L78 is now causing warnings about an undeclared dependency on GCC all over `homebrew-core`.

Yes. Better handling of this in `brew` is actually something I've wanted for some time now.

> For example, the `wheel` resource seems to be unnecessary for some formulas but not all. It is currently used by 14 formulas in `Homebrew/Core`. I think those formulae should...

Ubuntu 18.04 is EOL next year, so I strongly advise against switching to that since I don't want us to be having this discussion again so soon. Moving forward, I...

I'm not as concerned about security updates as I am about being able to build new software. My impression is that a given Ubuntu version going into ESM is a...

> @carlocab i.e. never `depends_on "gcc"`? Well, not _never_, but probably closer to it than where we are now. `depends_on "gcc"` is fine if you need `fortran`, but that's currently...

> Fortunately there is no tension between portability and bottle coverage now that we better understand the `glibc` bootstrapping process. Note: my earlier claim about the tradeoff between portability and...