-
Notifications
You must be signed in to change notification settings - Fork 6.6k
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 scripts] Remove deprecate functions vcpkg_*_cmake and vcpkg_fixup_cmake_targets #30070
[vcpkg scripts] Remove deprecate functions vcpkg_*_cmake and vcpkg_fixup_cmake_targets #30070
Conversation
…xup_cmake_targets
You cannot remove the function names. User ports may depend on them, and in manifest mode, even vcpkg ports will need them forever. |
Good point. |
Yes, it is technical debt which cannot be removed (except for a major release of vcpkg). |
At least we need a point in time to notify the user that they are about to be removed, like normal 3rd party libraries do. |
You cannot remove the scripts due to versioning? |
Wouldn't versioning affect these scripts? |
These are the unversioned global scripts. Manifest mode allows to install old port versions which rely on these scripts. |
I mean we could remove them if vcpkg-tool adds an implicit dep to a vcpkg-script port but that comes with its own set of advantages and disadvantages |
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.
I agree with @dg0yt .
Okay, so we need to modify our GitHub actions to report error when PR changes contains those deprecated functions right? |
Maybe upgrade selected keywords from warning to error. vcpkg/.github/workflows/untrustedPR.yml Line 30 in 02ad673
|
Close this PR since it's not appropriate. |
You could also issue a warning at the top of each deprecated function. |
Will do. |
Remove these deprecated functions completely since no port uses them.