-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
[thor] Pin SFML version to SFML 2 #43016
Conversation
308f666
to
5be97fb
Compare
5be97fb
to
513360e
Compare
"overrides": [ | ||
{ | ||
"name": "sfml", | ||
"version": "2.6.2" | ||
} |
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.
overrides
is for top-level projects. It has no effect for ports, classic mode or vcpkg CI.
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.
How does one pin dependency versions then in ports?
It shouldn't update beyond SFML 2.*
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.
You can't.
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.
So how does one update a dependency that is incompatible with other packages? Delete the other packages? Ignore them in the baseline?
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.
Update/patch as needed. Sometimes use baseline. Almost never delete.
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.
The source repo has been archived. A major version update can't be patched 😄
@BillyONeal do we just delete this package given that Thor has been archived and won't get an SFML 3 update? |
This port: * Blocks updating SFML to version 3 * Has been archived upstream since April 2022 * Is unpopular Replaces microsoft#43016
Closed as duplicate of #43067. |
./vcpkg x-add-version --all
and committing the result.Thor has been archived and won't be receiving any updates, as such the SFML version should be pinned to >=2.5
This is currently causing issues when trying to update SFML to SFML 3, see #42913
To be honest I don't know if I understood the versioning pinning correctly, so feel free to leave any review comments.