I guess I don’t really like the idea of a large company using a tool like Homebrew, I feel at that point they should write/include their own package manager.
I might be sounding pedantic, so feel free to ignore me if you’re a Homebrew fan, but it just irks me that the package manager is installed via curl’ing a shell script from their github project, and that the entire repo itself is stored on Github.
Even Microsoft has winget; dunno why a company the size of Apple can’t just roll a proper, secure way to distribute packages.
Also, as far as other package managers go, there’s Macports.
I guess I don’t really like the idea of a large company using a tool like Homebrew, I feel at that point they should write/include their own package manager.
I might be sounding pedantic, so feel free to ignore me if you’re a Homebrew fan, but it just irks me that the package manager is installed via curl’ing a shell script from their github project, and that the entire repo itself is stored on Github.
Even Microsoft has winget; dunno why a company the size of Apple can’t just roll a proper, secure way to distribute packages.
Also, as far as other package managers go, there’s Macports.
They have a proper, secure way to distribute packages - the app store. It just happens to be a GUI solution and not a CLI one.
Sure, exactly. So why do I need to install a third party CLI package manager for a first party suite of tools?
Like, xcode-select is able to grab dependencies. There’s no reason why a similar binary can’t be delivered with the porting sdk.