installation

Commandes d'installation supplémentaires

macOS

Homebrew Caskvérifié · 100%

brew install --cask p4

local Homebrew cask metadata

aperçu

Résumé du paquet

Use it to gain instant access to operations and complete control over the system

Liens du projet

Commandes et alias

p4
bin.macosx12arm64

historique

Historique du projet et usages

P4 CLI is the command-line client for Perforce P4, the centralized version-control platform formerly branded Helix Core. It connects local workspaces to P4 Server and exposes both everyday versioning operations and lower-level administrative capabilities.

Historique du projet

Christopher Seiwald started Perforce in 1995 around a version-control system originally called Perforce and commonly abbreviated P4. The product was renamed Helix Core in 2016 as Perforce expanded into a broader software portfolio.

In 2025, Perforce announced that Helix Core would again use the P4 name. Long-established command names such as p4 sync and p4 submit made the change a return to terminology already familiar to users.

Historique d'adoption

P4 became associated with centralized version-control deployments that must handle large repositories and binary assets. Perforce presents the wider P4 platform as serving demanding game, semiconductor, media, and enterprise engineering workflows.

Modes d'utilisation

Users configure a server address, identity, and client workspace, then run commands such as p4 sync, p4 edit, p4 submit, and p4 reconcile. Authentication tickets obtained through p4 login are kept in the P4TICKETS file.

Teams with several workspaces commonly set P4CONFIG to a filename such as .p4config. P4 searches the working directory and its parents for that file, allowing settings to follow each workspace.

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

The p4 executable is the canonical automation interface to P4 Server. It matters to package users because a small command-line client unlocks workspace synchronization, changelists, shelving, branching, merging, administration, and scripted CI access to an otherwise server-centered commercial ecosystem.

Its P4CONFIG search behavior is especially useful in developer environments: repository-local or parent-directory settings can automatically select the correct server, user, and workspace as the shell moves between projects.

Chronologie

1995: Christopher Seiwald founded Perforce around the version-control system commonly called P4.
2016: The original Perforce version-control product was renamed Helix Core.
2025: Perforce announced the return from the Helix Core product name to P4.

Related projects

P4 Server is the service operated by the client.
P4V provides a graphical client for the same server and workspace model.
P4Merge, P4 Admin, and P4 Code Review cover comparison, administration, and review workflows around P4.

Sources

posture de sécurité

Aucune couverture d'outil protégé trouvée pour le moment

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

Comportement d'installation

Aucun hook post-install Homebrew n’est enregistré dans les métadonnées de formule.
Aucune métadonnée de bottle Homebrew n’a été enregistrée.

Revue recommandée

Avant une utilisation sans surveillance par un agent, vérifiez si l'outil lit des identifiants en clair, écrit un état distant, publie des artefacts ou lance des plugins.

local files

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.

Configuration files

Config paths the tool may read or write during local use.

Unix: P4CONFIG-named file in the current working directorya parent directory, for example .p4config.txt
Windows: P4CONFIG-named file in the current working directorya parent directory, for example .p4config.txtPerforce settings stored by p4 set in the Windows registry

Credential files

Credential-bearing paths to review before unattended agent runs.

Unix: ~/.p4tickets
Windows: %USERPROFILE%\p4tickets.txtP4PASSWD in the Windows registry when set with p4 setP4V

exécutables

Exécutables installés

Commande	Type	Exposition	Note
`bin.macosx12arm64`	binaire	binaire de cask Homebrew	bin.macosx12arm64
`p4`	exécutable	exécutable indexé	Découvert depuis l'index local des exécutables.

fraîcheur

Version et fraîcheur

Ces signaux séparent l'âge de génération de la page, l'activité du gestionnaire de paquets et la comparaison avec les versions amont. Un retard de version n'est signalé que lorsqu'une URL de preuve et des versions comparables sont présentes.

page générée2026-11-04

version du gestionnaire2026.1,3089746

gestionnaire mis à jour2026-10-27

données localesOK

amontnot checked

dernière version détectéenon détecté

https://www.perforce.com/products/helix-core-apps/command-line-client

infoRelease/tag comparison is only available for GitHub repositories.https://www.perforce.com/products/helix-core-apps/command-line-clientconfiance none

métadonnées d'installation

Métadonnées du paquet

Clé du paquet	cask:p4
Version	2026.1,3089746
Gestionnaire de paquets	Homebrew Cask
Page du gestionnaire de paquets	https://formulae.brew.sh/cask/p4
Page d'accueil	https://www.perforce.com/products/helix-core-apps/command-line-client
Docs amont	https://www.perforce.com/products/helix-core-apps/command-line-client
Archive source	https://filehost.perforce.com/perforce/r26.1/bin.macosx12arm64/p4
Dernière mise à jour	2026-10-27T23:35:00+11:00
Pulse	updated
SHA-256	no_check
URL de téléchargement	https://filehost.perforce.com/perforce/r26.1/bin.macosx12arm64/p4
Bouteille	non enregistré
post-install Homebrew	non défini
Service	aucun déclaré

faits du registre

Détails de la base source

Source Database	Homebrew cask API
Tap	homebrew/cask
Full Token	p4
Names	Perforce Helix Command-Line Client (P4)
Conflicts With	Cask perforce
Artifacts	Binary 1 Target 1 Zap 1
Container	Type naked
Deprecated	no
Disabled	no

correspondances dans les bases sources

Autres enregistrements de gestionnaires de paquets

Les correspondances proviennent d’index externes de gestionnaires de paquets et restent séparées des liens de paquets Automic Vault locaux.

Nix95%

p4

nix profile install nixpkgs#p4

normalized package name match
Correspondance par : P4

nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/p4/p4/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

Chocolatey95%

p4

choco install p4

normalized package name match
Correspondance par : P4

Chocolatey community package catalog · community.chocolatey.org · Chocolatey community package catalog: p4 from https://community.chocolatey.org/api/v2/Packages?$filter=IsLatestVersion&$select=Id&$top=1000&$skiptoken='11','origin'

Scoop95%

main/p4

scoop install main/p4

normalized package name match
Correspondance par : P4

Scoop official bucket manifest trees · api.github.com · Scoop official bucket manifest trees: bucket/p4.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1

graphe de paquets

Les liens viennent du graphe local de relations entre paquets, des suppléments, des dépendances, des correspondances d'écosystèmes et de l'appartenance aux hubs.

piste source

Généré depuis les données du dépôt

Cette page est servie par av-web depuis l'artéfact SQLite privé des paquets généré par scripts/generate-pkg-sqlite.py.

Combined YAML source

View the package source record on GitHub.

combined/p4.yml

Sources utilisées

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

Installer p4 avec Homebrew Cask