Is your feature request related to a problem? Please describe.
APM is available in Homebrew core as apm, but the README and installation guide still lead with curl -sSL https://aka.ms/apm-unix | sh and advertise the custom tap command brew install microsoft/apm/apm as an alternative. This obscures the simpler package-manager-managed path and exposes new users to the standalone installer's system-directory and PATH behavior unnecessarily.
Public evidence:
Describe the solution you'd like
- Lead macOS onboarding with
brew install apm for users who already have Homebrew; explain that no custom tap is required.
- Document
brew upgrade apm as the update path for core installations. Do not recommend apm self-update for this distribution.
- Keep supported non-Homebrew installation choices visible, including for Linux users without Homebrew; do not require installing another package manager merely to install APM.
- Update the installation guide, quickstart, relevant CLI installation hints, and bundled APM usage guidance where applicable. Update the README subject to the repository's maintainer-approval requirement.
- Explain how existing custom-tap users can move to core without losing APM configuration or leaving conflicting executables. Establish the supported migration procedure before documenting commands; do not automatically uninstall or overwrite an existing installation.
- Describe the benefit accurately: package-manager ownership of installation and updates, not a claim that Homebrew eliminates all supply-chain risk.
Describe alternatives you've considered
Keeping the tap command as the primary Homebrew recommendation adds unnecessary distribution choice for new users now that core is available. Keeping the shell one-liner first and documenting user-local overrides still puts installer-specific configuration ahead of an existing package manager.
Additional context
This is a documentation and onboarding change, not a proposal to remove the standalone installer or immediately retire the tap. The core formula installs the Python package in a managed environment rather than invoking APM's standalone installer. No changes to private downstream repositories are in scope.
Is your feature request related to a problem? Please describe.
APM is available in Homebrew core as
apm, but the README and installation guide still lead withcurl -sSL https://aka.ms/apm-unix | shand advertise the custom tap commandbrew install microsoft/apm/apmas an alternative. This obscures the simpler package-manager-managed path and exposes new users to the standalone installer's system-directory and PATH behavior unnecessarily.Public evidence:
brew upgrade apm.Describe the solution you'd like
brew install apmfor users who already have Homebrew; explain that no custom tap is required.brew upgrade apmas the update path for core installations. Do not recommendapm self-updatefor this distribution.Describe alternatives you've considered
Keeping the tap command as the primary Homebrew recommendation adds unnecessary distribution choice for new users now that core is available. Keeping the shell one-liner first and documenting user-local overrides still puts installer-specific configuration ahead of an existing package manager.
Additional context
This is a documentation and onboarding change, not a proposal to remove the standalone installer or immediately retire the tap. The core formula installs the Python package in a managed environment rather than invoking APM's standalone installer. No changes to private downstream repositories are in scope.