-
Notifications
You must be signed in to change notification settings - Fork 199
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
[Merged by Bors] - feat(cdk): supply arch
tag on publish if not set
#3080
[Merged by Bors] - feat(cdk): supply arch
tag on publish if not set
#3080
Conversation
@@ -498,6 +507,27 @@ pub fn package_verify_with_readio<R: std::io::Read + std::io::Seek>( | |||
Ok(()) | |||
} | |||
|
|||
fn augment_arch(package_meta: &mut PackageMeta, target: Option<&str>) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't augment_arch just accept a target instead of Option. Why call it at all if target is None? Or is this a useful pattern? Thinking about this because we may other optional package tags in the future...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Indeed, moving a if
outside and making augment_arch
accept target
looks nicer. I changed it. Thanks.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
bors r+ |
The presence of `arch` tag is required for multi-arch packaging. If it is not specified in `package-meta.yaml` we supply it before publishing (to be precise, before the package assembling).
Build failed: |
bors retry |
The presence of `arch` tag is required for multi-arch packaging. If it is not specified in `package-meta.yaml` we supply it before publishing (to be precise, before the package assembling).
Pull request successfully merged into master. Build succeeded: |
arch
tag on publish if not setarch
tag on publish if not set
The presence of
arch
tag is required for multi-arch packaging. If it is not specified inpackage-meta.yaml
we supply it before publishing (to be precise, before the package assembling).