gnu-tar: prevent opportunistic gettext linkage

[alebcay]

• Have you followed the guidelines for contributing?
• Have you ensured that your commits follow the commit style guide?
• Have you checked that there aren't other open pull requests for the same formula update/change?
• Have you built your formula locally with HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>, where <formula> is the name of the formula you're submitting?
• Is your test running fine brew test <formula>, where <formula> is the name of the formula you're submitting?
• Does your build pass brew audit --strict <formula> (after doing HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>)? If this is a new formula, does it pass brew audit --new <formula>?

---

This addresses #155992. No bottles needed since CI tightly controls deps present at build time; the issue is only encountered when users build from source.

[fxcoudert]

I don't understand the logic. You're saying CI is not affected, “the issue is only encountered when users build from source”, but it would fix something that happens in CI?

[Bo98]

You're saying CI is not affected, “the issue is only encountered when users build from source”, but it would fix something that happens in CI?

It could happen in CI if built among something else that pulled in gettext, yes. The last gnu-tar bottle was built in isolation however without gettext and thus the existing bottles are fine and don't have this linkage. The issue here only happens with gettext installed.