Skip to content
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

Closed
wants to merge 1 commit into from

Conversation

eXpl0it3r
Copy link
Contributor

@eXpl0it3r eXpl0it3r commented Dec 30, 2024

  • Changes comply with the maintainer guide.
  • SHA512s are updated for each updated download.
  • The "supports" clause reflects platforms that may be fixed by this new version.
  • Any fixed CI baseline entries are removed from that file.
  • Any patches that are no longer applied are deleted from the port's directory.
  • The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
  • Only one version is added to each modified port's versions file.

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.

@eXpl0it3r eXpl0it3r force-pushed the feature/thor-fix branch 4 times, most recently from 308f666 to 5be97fb Compare December 30, 2024 20:37
@eXpl0it3r eXpl0it3r marked this pull request as ready for review December 30, 2024 21:02
Comment on lines +18 to +22
"overrides": [
{
"name": "sfml",
"version": "2.6.2"
}
Copy link
Contributor

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.

Copy link
Contributor Author

@eXpl0it3r eXpl0it3r Dec 30, 2024

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.*

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You can't.

Copy link
Contributor Author

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?

Copy link
Contributor

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.

Copy link
Contributor Author

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 😄

@eXpl0it3r
Copy link
Contributor Author

@BillyONeal do we just delete this package given that Thor has been archived and won't get an SFML 3 update?

BillyONeal added a commit to BillyONeal/vcpkg that referenced this pull request Jan 2, 2025
This port:

* Blocks updating SFML to version 3
* Has been archived upstream since April 2022
* Is unpopular

Replaces microsoft#43016
@BillyONeal BillyONeal mentioned this pull request Jan 2, 2025
@LilyWangLL
Copy link
Contributor

Closed as duplicate of #43067.

@LilyWangLL LilyWangLL closed this Jan 3, 2025
@eXpl0it3r eXpl0it3r deleted the feature/thor-fix branch January 3, 2025 11:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants