# Installer perforce avec Homebrew Cask

Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de perforce pour les workflows d'agents IA.

## installation

```sh
sudo av install cask:perforce
```

Commandes d'installation supplémentaires:

### macOS

- Homebrew Cask (100%):

```sh
brew install --cask perforce
```

  Preuve: local Homebrew cask metadata

## Faits du paquet

- **Clé du paquet:** cask:perforce
- **Gestionnaire de paquets:** Homebrew Cask
- **Page du gestionnaire de paquets:** <https://formulae.brew.sh/cask/perforce>
- **Version:** 2026.1,2972966
- **Résumé source:** Version control
- **Page d'accueil:** <https://www.perforce.com/>
- **Docs amont:** <https://www.perforce.com/>
- **Archive source:** <https://filehost.perforce.com/perforce/r26.1/bin.macosx12arm64/helix-core-server.tgz>
- **Dernière mise à jour:** 2026-06-11T20:15:03Z
- **Généré:** 2026-08-04T22:13:35+00:00

## exécutables

- p4 (binaire)
- p4broker (binaire)
- p4d (binaire)
- p4p (binaire)
- p4broker (alias)
- p4d (alias)
- p4p (alias)

## Comportement d'installation

- hook post-installation: non défini
- Précautions: Instructions on using the Helix Versioning Engine are available in $HOMEBREW_PREFIX/Caskroom/perforce/2026.1,2972966
- Bouteille: non disponible

## Version et fraîcheur

- page générée: 2026-08-04
- version du gestionnaire: 2026.1,2972966
- gestionnaire mis à jour: 2026-06-11
- données locales: OK
- dépôt amont: https://www.perforce.com/
- info: Release/tag comparison is only available for GitHub repositories.
## Historique du projet et usages

Perforce P4 is Perforce's centralized version-control platform, formerly branded Helix Core, aimed at teams that need scalable source and digital-asset management.

### Historique du projet

Perforce's current product page identifies P4 as the renamed Helix Core product and presents it as the server foundation for the broader P4 platform.

### Historique d'adoption

Perforce positions P4 as especially common in game development and large digital-content production, citing adoption by 19 of the top 20 AAA game studios.

### Modes d'utilisation

Package-manager users install server-side components such as p4d, p4p, and p4broker, then administer repositories through Perforce's command-line and server documentation.

### Pourquoi les passionnés de paquets s'y intéressent

P4 matters in package collections because it is a long-lived proprietary SCM system with Unix-friendly server binaries, environment-variable-driven clients, and a distinct operational model from Git-centered tooling.

### Chronologie

- 1997: Perforce release notes track changes from Release 97.3 onward.
- 2025: Perforce announced Helix Core was rebranded as P4.

### Related projects

- P4V, P4 Proxy, P4 Broker, P4 DAM, and P4 Plan are related Perforce tools around the same version-control platform.

### Sources

- <https://help.perforce.com/helix-core/server-apps/cmdref/current/content/CmdRef/P4TICKETS.html>
- <https://www.perforce.com/blog/vcs/introducing-the-p4-platform>
- <https://www.perforce.com/products/helix-core>
- <https://www.perforce.com/release-notes/helix-core>


## Notes de sécurité

Aucun manifest local de gestion des secrets correspondant n'a été trouvé pour perforce. Les métadonnées de paquet restent publiées ici afin que la couverture future dispose d'une URL stable.



## Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.


## Credential files

- Unix: ~/.p4tickets
- Windows: %USERPROFILE%\p4tickets.txt
## Détails de la base source

- **Source Database:** Homebrew cask API
- **Tap:** homebrew/cask
- **Full Token:** perforce
- **Names:** Perforce Helix Broker (P4Broker), Perforce Helix Command-Line Client (P4), Perforce Helix Core Server, Perforce Helix Proxy (P4P), Perforce Helix Versioning Engine (P4D)
- **Conflicts With:** Cask: p4
- **Artifacts:** Binary: 4, Target: 4
- **Deprecated:** no
- **Disabled:** no

## Autres enregistrements de gestionnaires de paquets

- MacPorts - perforce: normalized package name match | MacPorts ports tree: devel/perforce/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1
- Nix - p4: installed executable or alias match | nixpkgs package indexes: pkgs/by-name/p4/p4/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
- Nix - p4d: installed executable or alias match | nixpkgs package indexes: pkgs/by-name/p4/p4d/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
- Chocolatey - p4: installed executable or alias match | Chocolatey community package catalog: p4 from http://community.chocolatey.org/api/v2/Packages?$filter=IsLatestVersion&$select=Id&$top=1000&$skiptoken='11','openconnect-gui'
- Scoop - main/p4: installed executable or alias match | Scoop official bucket manifest trees: bucket/p4.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1


## Liens liés

- [Homebrew Cask packages](https://pkg.so/fr/homebrew-cask-packages/) - Generated from Homebrew Cask package-manager metadata.
- [Homebrew Cask binaries](https://pkg.so/fr/homebrew-cask-binaries/) - Cask artifact metadata includes a binary.

## Combined YAML source

View the package source record on GitHub. [combined/perforce.yml](https://github.com/mxcl/pkgdb/blob/main/combined/perforce.yml)


## Sources

- pkg.so package database
- package-page enrichment
- curated configuration and credential file locations
- curated package history
- package version freshness
- pkgdb category and tag curation
- package relationship graph
- external package-manager database matches
- cross-ecosystem install command graph