Re: [PATCH v3 1/2] ci: drop quarantine removal for macos perforce binaries

[Patrick Steinhardt <ps@pks.im>]

On Mon, Oct 26, 2026 at 09:54:24AM +0000, Harald Nordgren via GitGitGadget wrote:
> From: Harald Nordgren <haraldnordgren@gmail.com>
> 
> A file downloaded with wget never gets com.apple.quarantine set,
> only Safari, Finder, and AirDrop apply that attribute through the
> LaunchServices quarantine API.

This is the explanation why we can remove the flag, but we haven't even
talked about the observation or what we want to do.

> 5ed9fc3fc8 (ci: prevent `perforce` from being quarantined,
> 2020-02-27) added this to stop p4d -V from hanging on a GUI

Nit: you start talking about "this" without even saying what "this" is.

> confirmation dialog that never comes on a CI box, back when perforce
> was installed via Homebrew's --no-quarantine cask flag. When
> 49af448197 (ci: reintroduce prevention from perforce being
> quarantined in macOS, 2022-05-12) replaced that with a plain wget and
> tar download, it kept an xattr -d call as a precaution while noting
> that call already does nothing on GitHub Actions. It has been a
> silent no-op ever since.

So the question is what this does on GitLab CI. [1] will answer that
question once the pipeline has succeeded.

Patrick

[1]: https://gitlab.com/gitlab-org/git/-/merge_requests/714