-
Notifications
You must be signed in to change notification settings - Fork 6.7k
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
[vcpkg_configure_cmake] Partially revert #26959 #28483
Conversation
We must avoid significant breaking changes to the sets of scripts coupled to the vcpkg tool version.
I don't care too much about this revert but why can vcpkg not break stuff when there is a triplet escape hatch to unbreak? |
Because breaking stuff in this way causes users that upgrade the tool (not their libraries) to be broken. Our intent is that upgrading the vcpkg tool, if you're using manifests & versioning, will not break you. This is essential to promote and enable all users to quickly adopt new versions of the tool. |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
We must avoid significant breaking changes to the sets of scripts coupled to the vcpkg tool version.
What does your PR fix?
Partially addresses #28386. @craigscott-crascit has identified this as a breaking change which is not permissible in the helper scripts bundled with the tool.