Git development
 help / color / mirror / Atom feed
From: "Harald Nordgren via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Harald Nordgren <haraldnordgren@gmail.com>,
	Harald Nordgren <haraldnordgren@gmail.com>
Subject: [PATCH v2] ci: drop no-op gettext link on macOS
Date: Mon, 14 Sep 2026 07:09:09 +0000	[thread overview]
Message-ID: <pull.2402.v2.git.git.1789369749450.gitgitgadget@gmail.com> (raw)
In-Reply-To: <pull.2402.git.git.1789199739368.gitgitgadget@gmail.com>

From: Harald Nordgren <haraldnordgren@gmail.com>

Homebrew's gettext formula used to be keg-only, meaning brew would
install it into the Cellar without linking its headers, libraries, or
utilities like msgfmt anywhere on the default search paths, to avoid
clashing with software that already ships its own gettext. `brew link
--force gettext` overrode that restriction so the keg-only install
became visible on the paths git's build and tests rely on.

Homebrew dropped gettext's keg-only status in 2020
(https://github.com/Homebrew/homebrew-core/pull/53489), so a fresh
install now links into the prefix by itself. `brew link --force`
against an already-linked keg has nothing left to override, and only
produces a spurious "Already linked" warning in every macOS job's
log.

Signed-off-by: Harald Nordgren <haraldnordgren@gmail.com>
---
    ci: drop no-op gettext link on macOS
    
    Gettext is already linked on the macOS CI runner image, so the forced
    relink was a no-op that only produced a spurious "Already linked"
    warning in every macOS job's log.
    
    Changes in v2:
    
     * Clarify problem in commit message.

Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-2402%2FHaraldNordgren%2Fci-drop-noop-gettext-link-v2
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-2402/HaraldNordgren/ci-drop-noop-gettext-link-v2
Pull-Request: https://github.com/git/git/pull/2402

Range-diff vs v1:

 1:  9af619d085 ! 1:  39922c8e97 ci: drop no-op gettext link on macOS
     @@ Metadata
       ## Commit message ##
          ci: drop no-op gettext link on macOS
      
     -    gettext ships already linked on the macOS CI runner image, so this
     -    command never links anything. It only emits a spurious "Already
     -    linked" warning in every macOS job's log.
     +    Homebrew's gettext formula used to be keg-only, meaning brew would
     +    install it into the Cellar without linking its headers, libraries, or
     +    utilities like msgfmt anywhere on the default search paths, to avoid
     +    clashing with software that already ships its own gettext. `brew link
     +    --force gettext` overrode that restriction so the keg-only install
     +    became visible on the paths git's build and tests rely on.
     +
     +    Homebrew dropped gettext's keg-only status in 2020
     +    (https://github.com/Homebrew/homebrew-core/pull/53489), so a fresh
     +    install now links into the prefix by itself. `brew link --force`
     +    against an already-linked keg has nothing left to override, and only
     +    produces a spurious "Already linked" warning in every macOS job's
     +    log.
      
          Signed-off-by: Harald Nordgren <haraldnordgren@gmail.com>
      


 ci/install-dependencies.sh | 1 -
 1 file changed, 1 deletion(-)

diff --git a/ci/install-dependencies.sh b/ci/install-dependencies.sh
index 2f61fbb07c..2903c39fab 100755
--- a/ci/install-dependencies.sh
+++ b/ci/install-dependencies.sh
@@ -117,7 +117,6 @@ macos-*)
 	export HOMEBREW_NO_AUTO_UPDATE=1 HOMEBREW_NO_INSTALL_CLEANUP=1
 	# Uncomment this if you want to run perf tests:
 	# brew install gnu-time
-	brew link --force gettext
 
 	mkdir -p "$CUSTOM_PATH"
 	wget -q "$P4WHENCE/bin.macosx12arm64/helix-core-server.tgz" &&

base-commit: 47ce80527c56f462cb97db4ca8125342204d3783
-- 
gitgitgadget

  parent reply	other threads:[~2026-09-14  7:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-12  7:55 [PATCH] ci: drop no-op gettext link on macOS Harald Nordgren via GitGitGadget
2026-09-14  6:25 ` Patrick Steinhardt
2026-09-14  6:57   ` Harald Nordgren
2026-09-14  7:53     ` Patrick Steinhardt
2026-09-14  8:50       ` Harald Nordgren
2026-09-14  7:09 ` Harald Nordgren via GitGitGadget [this message]
2026-09-26  4:36   ` [PATCH v2] " Junio C Hamano
2026-09-26 13:33     ` Harald Nordgren

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=pull.2402.v2.git.git.1789369749450.gitgitgadget@gmail.com \
    --to=gitgitgadget@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=haraldnordgren@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox