Skip to content
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

getbinariesfromquay: Remove - separating arch from variant #38

Merged
merged 1 commit into from
Jan 20, 2021

Conversation

mmlb
Copy link
Contributor

@mmlb mmlb commented Jan 20, 2021

Description

Renames binaries to be more consistent in and of itself and also compared to other Go projects that provide multi-arch binaries.

Why is this needed

@gianarb asked me to rename the binaries in tinkerbell/smee#122 to match this scheme, but I think that this PR is the better directon.

This naming scheme seemed weird to me so I went looking around at other
Go projects. None of the projects that I found that had multi-arch
release binaries used this scheme, instead they just append the variant
to arch. Appending the variant to the arch also makes a lot of sense if
you think of the naming schme as $binary-$os-$cpu and
$cpu=$arch$variant. Keeping arch and variant together as $cpu is also
more consistent, and consitency is great :D.

Signed-off-by: Manuel Mendez <[email protected]>
@mmlb mmlb added the breaking-change Denotes a PR that introduces potentially breaking changes that require user action. label Jan 20, 2021
@mmlb mmlb requested a review from gianarb January 20, 2021 14:40
@mmlb mmlb removed the request for review from gauravgahlot January 20, 2021 14:51
@mmlb mmlb added the ready-to-merge Signal to Mergify to merge the PR. label Jan 20, 2021
@mergify mergify bot merged commit ce7a79b into master Jan 20, 2021
@mmlb mmlb deleted the change-variant-names-to-common-format branch January 20, 2021 15:04
ttwd80 pushed a commit to ttwd80/tinkerbell-playground that referenced this pull request Sep 7, 2024
…l#38)

## Description

Renames binaries to be more consistent in and of itself and also compared to other Go projects that provide multi-arch binaries.

## Why is this needed

@gianarb asked me to rename the binaries in tinkerbell/smee#122 to match this scheme, but I think that this PR is the better directon.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking-change Denotes a PR that introduces potentially breaking changes that require user action. ready-to-merge Signal to Mergify to merge the PR.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants