-
-
Notifications
You must be signed in to change notification settings - Fork 12.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gpatch: add gpatch binary to avoid conflict with macOS patch #174687
Conversation
Does this patch work if |
this is a good question. Does any of the homebrew maintainers know if it's possible to change the behaviour of a package in a keg-only context? |
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
not stale. Waiting for answer |
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
not stale. Waiting for answer |
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
not stale. Waiting for answer from the maintainers |
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
not stale. Waiting for answer from the maintainers |
🤖 An automated task has requested bottles to be published to this PR. |
…ports expose gpatch as gpatch Homebrew changed behaviour in Homebrew/homebrew-core#174687
…ports expose gpatch as gpatch Homebrew changed behaviour in Homebrew/homebrew-core#174687
…ports expose gpatch as gpatch Homebrew changed behaviour in Homebrew/homebrew-core#174687
…tch binary to gpatch (see Homebrew/homebrew-core#174687)
…ports expose gpatch as gpatch Homebrew changed behaviour in Homebrew/homebrew-core#174687
…tch binary to gpatch (see Homebrew/homebrew-core#174687)
HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>
, where<formula>
is the name of the formula you're submitting?brew test <formula>
, where<formula>
is the name of the formula you're submitting?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>
?This ensures there is a simple way to distinguish between macOS patch (/usr/bin/patch) and homebrew gpatch. Macports installs its version as gpatch and so does BSDs but Homebrew seems to be the only that does not do that.
This PR adds a link rather than rename the binary to keep backward compatibility with the old behaviour.