plink1 1.9.0-b.7.11 (new formula) - #301422
Open
BenjaminDEMAILLE wants to merge 2 commits into
Open
Conversation
BenjaminDEMAILLE
force-pushed
the
plink-1.9
branch
from
August 30, 2026 11:44
d2562e5 to
69285ec
Compare
SMillerDev
reviewed
Aug 31, 2026
BenjaminDEMAILLE
force-pushed
the
plink-1.9
branch
from
August 31, 2026 22:15
42d2537 to
002ca77
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>?brew test <formula>?brew audit --strict <formula>(after doingHOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>)? If this is a new formula, does it passbrew audit --new <formula>?AI-assisted contribution by Claude Code (Claude Opus 5) of ~85% of the work: the AI wrote the formula and ran
brew style,HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source,brew testandbrew audit --strict --newon my machine. I reviewed the formula and those results before opening this PR, and will answer maintainer questions and review comments myself. The commits carry no AI attribution trailer.Built and tested locally on macOS 26.6.2 running arm64.
PLINK 1.9 is the still-maintained 1.x line of PLINK; it is not superseded by PLINK 2.0 (
plink-ng, added in #297195). Upstream's README states that active feature development for 1.9 ended in 2016 but the 2.0 line is "under active development" with "most basic features other than non-concatenating merge" in place, so the two are installed side by side in practice. Upstream still tags 1.9 patch releases:v1.9.0-b.7.11is from August 2025.Both lines live in the same repository, so this builds the
1.9/subdirectory of thechrchang/plink-ngtarball.ZLIB=-lzis needed because the Makefile defaults to a vendored zlib that is not shipped in the release tarball; on LinuxBLASFLAGSis overridden because the default points at ATLAS.The formula is named
plink1but installs the binary under its upstream nameplink, which is what the documentation and existing pipelines expect. That collides withputty, which shipsbin/plink(PuTTY Link):The two audiences barely overlap, and
brew audit --newdoes not flag the collision on its own, so the second commit is a deliberate choice rather than something CI forced: without a declaration, a user who has both installed gets an opaqueTarget /opt/homebrew/bin/plink already existslink failure instead of a clear conflict message.puttyalready declaresconflicts_with "pssh"for the same reason.Happy to install the binary as
plink1instead if you would rather not touchputty; that would drop the second commit entirely.