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
[teemo] Update version to v2.2. #18551
Conversation
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.
Could you please run vcpkg x-add-version teemo
to update version files and commit the changes?
I have modified version to v2.2, please recheck again. |
Please update version files via the above command. |
Sorry, It's my mistake. |
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.
Thanks for the PR!
ports/teemo/CONTROL
Outdated
Version: 2.1 | ||
Build-Depends: curl[non-http] | ||
Version: 2.2 | ||
Build-Depends: curl[non-http,openssl] |
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.
Why does this require curl[openssl]
?
- We default to using the Win32 APIs on Windows, not openssl. At a minimum, this needs to be qualified to non-windows platforms.
- My understanding is that this is a behavior, not an API.
teemo
shouldn't be able to notice whether curl is built with or without SSL support and it's reasonable that a user might want to useteemo
on top of curl without openssl.
If you want users of teemo to be able to request specifically OpenSSL support, then perhaps instead teemo should have an openssl
feature that depends on curl's openssl
feature.
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.
teemo is cross-platfrom, not noly support windows.
If you want libcurl support https, openssl is not optional.
Now https is very popular.
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.
Our default build of libcurl does support https on windows -- but via the Win32 APIs, not openssl.
Could you instead try using:
Build-Depends: curl[non-http,openssl] | |
Build-Depends: curl[core], openssl |
and let us know specifically what does not work for you? If a user's project wants to support non-http protocols, the user can easily ask for that on the command line via vcpkg install teemo curl[non-http]
.
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.
Port curl has the feature 'ssl' which chooses an implementation (another feature) depending on the platform. So there is no need to hardcode 'openssl'.
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.
@dg0yt @ras0219-msft
I think both of yours opinion are right, I have updated to:
Build-Depends: curl[core]
@winsoft666 |
Describe the pull request
What does your PR fix?
Fixes Build-Depends library.
Which triplets are supported/not supported? Have you updated the CI baseline?
<all / linux, windows, ...>, <Yes/No>
Does your PR follow the maintainer guide?
Yes
If you have added/updated a port: Have you run
./vcpkg x-add-version --all
and committed the result?<Yes / I am still working on this PR>
If you are still working on the PR, open it as a Draft: https://github.blog/2019-02-14-introducing-draft-pull-requests/