-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make released binary names more consistent #16667
Conversation
Looking at https://github.com/containers/podman/releases/tag/v4.3.1, it's not explicit which arch the podman-remote-static binary is built for, so this commit adds an -$(goarch) suffix to it. It builds both arm64 and amd64 binaries as I need both for crc. Signed-off-by: Christophe Fergeau <[email protected]>
This is more consistent with the name of the other released files, and makes identification of the binaries easier among the Windows/macOS ones. Related: containers#16612 Signed-off-by: Christophe Fergeau <[email protected]>
All files released in https://github.com/containers/podman/releases/tag/v4.3.1 use -arm64 for the arch name except podman-installer-macos-aarch64.pkg Related: containers#16612 Signed-off-by: Christophe Fergeau <[email protected]>
LGTM, but I'd prefer if someone more experienced with Makefiles review before merge. |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cfergeau, mheon The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/lgtm |
This PR changes the name of some of the binaries which go to
https://github.com/containers/podman/releases/
It renames
podman-release-static
topodman-release-static-linux_{amd64,arm64}
,and renames
podman-installer-macos-aarch64.pkg
topodman-installer-macos-arm64.pkg
automation/scripts relying on these file names which are not stored in
github.com/containers/podman will need to be adjusted for these changes.
This fixes #16612
Does this PR introduce a user-facing change?