Daniel Nachun

I believe you can fix the `variably modified X at file scope` errors by using `enum` rather than `const char` or `const long long int`: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93082. Apparently this was allowed...

We actually can use GCC 11 to build in Homebrew, but the error still happens there. According to the Clang issue linked above, it seems this may have been allowed...

@RJVB if it's possible for this fix to be added as a commit we can then use that commit to as a patch for our package. If you think it...

I am wondering if, as a starting point, we should make a `test-dependent` workflow which is given the names of the dependent and its dependency, the platform to test, and...

> > 2. Add a `DownloadStrategy` that uses the HTTP gem from Ruby while installing `curl` and its dependencies - `git` can be installed afterward with brewed `curl`. This is...

I'm in agreement with all of the above - ideally we shouldn't even have `-L$HOMEBREW_PREFIX/lib` or `-Wl,-rpath,$HOMEBREW_PREFIX` in our LDFLAGS on any OS, as these links can disappear with `brew...

No major objections here, but one major question - unlike on macOS, I'm not sure we want to keep the 16.04 bottle if a 22.04 bottle exists, so I think...

Right, I should have said if the bottle line in the formula could be deleted. Certainly the packge itself doesn't have to be removed.

Should we rename `atk` and `at-spi2-atk` to `at-spi2-core`?

This should depend on `gtk+4` now instead of `gtk+3`.