Hi Alan! 👋
First of all, thank you for Gentleman.Dots. I installed it on Arch Linux and had a great time exploring the installer and the codebase.
While installing through the Homebrew tap, I noticed something that might simply be an outdated formula.
What I observed
brew info gentleman-dots reports:
However, the main repository is already tagged as:
I also checked the Homebrew formula (Formula/gentleman-dots.rb), which is currently pinned to:
Why I noticed it
On Arch Linux, the installation initially failed because pacman could not find carapace:
error: target not found: carapace
While investigating, I compared v2.12.1 and v2.12.2 and noticed that v2.12.2 introduces the runNativeWithBrewFallback() logic for native package managers.
I then built and ran the installer directly from the current source (v2.12.2), and the installation completed successfully on the same machine.
Question
Is the Homebrew tap simply waiting to be updated to v2.12.2, or is there another release process involved?
If the formula is meant to track the latest release, it looks like Homebrew users are still receiving v2.12.1, while the repository has already released v2.12.2.
I hope this information is useful. If I misunderstood part of the release process, please let me know.
Thanks again for the project! 🙂
Hi Alan! 👋
First of all, thank you for Gentleman.Dots. I installed it on Arch Linux and had a great time exploring the installer and the codebase.
While installing through the Homebrew tap, I noticed something that might simply be an outdated formula.
What I observed
brew info gentleman-dotsreports:However, the main repository is already tagged as:
I also checked the Homebrew formula (
Formula/gentleman-dots.rb), which is currently pinned to:Why I noticed it
On Arch Linux, the installation initially failed because
pacmancould not findcarapace:While investigating, I compared
v2.12.1andv2.12.2and noticed thatv2.12.2introduces therunNativeWithBrewFallback()logic for native package managers.I then built and ran the installer directly from the current source (
v2.12.2), and the installation completed successfully on the same machine.Question
Is the Homebrew tap simply waiting to be updated to
v2.12.2, or is there another release process involved?If the formula is meant to track the latest release, it looks like Homebrew users are still receiving
v2.12.1, while the repository has already releasedv2.12.2.I hope this information is useful. If I misunderstood part of the release process, please let me know.
Thanks again for the project! 🙂