homebrew-core

Reproducible… but unsupported. Nice. https://github.com/Homebrew/homebrew-core/issues/108964#issu...

https://github.com/Homebrew/homebrew-core/blob/master/Formul... -> https://www.npmjs.com/package/@bitwarden/cli -> https://github.com/bitwarden/clients/tree/cli-v2023.10.0

That's quite the sparse list of packages: https://github.com/lodosgroup/package-builds/tree/linux-amd6... They also don't seem to think this is going to catch on and thus haven't sharded the directory list as homebrew-core recently had to do: https://github.com/Homebrew/homebrew-core/tree/master/Formul... There are already SO MANY build-from-source specifications it is insaneo to start a new project without the ability to at least import from any one of them, especially since it seems this toy goes with the "shell script and good luck" approach https://github.com/lodosgroup/package-builds/blob/linux-amd6... (not even having the forethought to provide a download helper and/or turn on `curl -f` because the network is always reliable and servers never 503 amirite?)

It's at the discretion of the package maintainer, but it's pretty common. Just look at the `Formula.rb` for any standalone app in Python or Lua. Example: https://github.com/Homebrew/homebrew-core/blob/66c42fbd814b3... I think using per-project venv is still the sensible thing to do, not just in Python but using the equivalent in Lua (hererocks), Ruby (Bundler), etc. This is for system-wide installations of standalone CLI tools and other "apps". However if you do find something on PyPI that is a standalone app, but isn't in Homebrew, you can create an isolated env for it automatically using Pipx https://pypa.github.io/pipx/.

Whoa, that is a weird one. Do you know what version of Python you have from Homebrew? It looks like that package is correctly listed in the formula: https://github.com/Homebrew/homebrew-core/blob/a0048881ba9a2...

This won't impact infracost, Alistair just responded to it: https://github.com/Homebrew/homebrew-core/pull/139538#issuec...

Note for whatever it is worth that the Homebrew-owned version rebuilds these from source -- https://github.com/Homebrew/homebrew-core/pull/139538/files#.... This is also typical in the Linux packaging ecosystem, but typically involving packaging dependencies explicitly too, which is likely why Vault &co never landed in a distro's package set prior to the license change. The Hashicorp variants copy the release builds: https://github.com/hashicorp/homebrew-tap/blob/master/Formul...

True, Hashi can cask it just fine if they wanted to continue to distribute through homebrew. I doubt they would though, they have already been recommending direct binary installation from their servers for the past few years. That is how the installation documentation for Terraform has been for a while. The bigger impact is on other tools that have terraform as a dependency, as seen here: https://github.com/Homebrew/homebrew-core/pull/139538#pullre... Tools like atlantis and infracost are also getting removed since they depend on Terraform. So it is going to make distribution a little harder for those smaller tools. The good news is that the thread does say that they are holding off to allow those tools to update their dependencies to an alternative like OpenTofu when it becomes stable or to remove the dependency altogether. But the real

From my looking around, Homebrew's Python 3.11 has specific binaries for each macOS and CPU architecture https://github.com/Homebrew/homebrew-core/blob/c1321e2629203... A comment in Homebrew's formula says that Homebrew adds the --enable-optimizations flag during compilation because Homebrew has separate binaries whereas the official Python release doesn't add this flag because "they want one build that will work across many macOS releases" https://github.com/Homebrew/homebrew-core/blob/c1321e2629203... and it looks to me that pyenv just installs the official binary https://github.com/pyenv/pyenv/blob/28e7000b485bff61235d8a69... So I would expect it to be the other way around, Homebrew's Python should be faster.

This is incorrect. Nixpkgs updated to 2.12 on the same day as Homebrew. - Nixpkgs (3 days ago): https://nixpk.gs/pr-tracker.html?pr=238031 - Homebrew (3 days ago): https://github.com/Homebrew/homebrew-core/pull/133968 Your link refers to the 23.05 stable release channel, so it'd likely stay at 2.11. Package updates don't get backported to stable channels except for fixes. Additionally, the package search page probably isn't updated in real time so the version might be slightly out of sync. Nixpkgs is generally quick to update packages because Nix encourages automation.

Thanks! Homebrew formula in review https://github.com/Homebrew/homebrew-core/pull/132580

Well that's unfortunate, `brew update` does not show any 2.40.1: https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/... even though the tag was cut last week: https://github.com/git/git/releases/tag/v2.40.1 Thank goodness `brew edit git` still works ... for now :-/