# 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
- **Version:** 2026.1,2972966
- **Résumé source:** Version control
- **Page d'accueil:** <https://www.perforce.com/>
- **Dernière mise à jour:** 2026-06-11T20:15:03Z
- **Généré:** 2026-08-03T19:37:03+00:00

## exécutables

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

## Comportement d'installation

- Bouteille: non disponible

## Version et fraîcheur

- page générée: 2026-08-03
- version du gestionnaire: 2026.1,2972966
## 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 Nucleus 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
## 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


## 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
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation
- external package-manager database matches
- cross-ecosystem install command graph