Yes, so we should move to a source-based package manager and build system, like ...

adastra22 · 2024-09-16T23:12:59.000000Z

There are plenty of options for that on macOS, the most common being homebrew and MacPorts.

Hamuko · 2024-09-17T04:33:00.000000Z

Homebrew defaults to downloading binaries.

adastra22 · 2024-09-17T09:21:14.000000Z

Defaults to. You can tell it to compile yourself, if that matters to you. I don’t see what the issue is here. Why is it a problem that it defaults to binary distribution?

Hamuko · 2024-09-17T19:22:13.000000Z

The biggest problem is that the defaulting to binary distribution also means that building from source is unsupported.

>Building from source takes a long time, is prone to failure, and is not supported.

Having issues building your Homebrew packages from source? Well, you better not take it to the bug tracker.

fredoliveira · 2024-09-17T21:31:25.000000Z

> The biggest problem is that the defaulting to binary distribution also means that building from source is unsupported.

I don't think it means that at all. They're both clearly supported by homebrew — one just happens to be the default. You can always use -s or --build-from-source to build whatever package you are installing.

Hamuko · 2024-09-18T04:11:34.000000Z

I mean, it is quite clearly said in the documentation that building from source is not supported.

adastra22 · 2024-09-18T05:52:17.000000Z

It's running the same compilation steps that the binaries are produced from. If you can get a binary through homebrew, you can compile it from source. It's just unsupported in the sense that the developers don't want to spend their time chasing down build issues on individual user's systems. You're on your own if you break your local build environment.

(Ignoring the packages that are just wrappers around closed source software and fetch binaries whether you compile from source or not. Those are the exception, not the rule.)