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

[meson] update to 1.3.2 #37335

Closed
wants to merge 1 commit into from
Closed

[meson] update to 1.3.2 #37335

wants to merge 1 commit into from

Conversation

vipcxj
Copy link
Contributor

@vipcxj vipcxj commented Mar 9, 2024

The latest gstreamer require meson >= 1.1, So I update it. I have update gstreamer to 1.24.0 in my local repo, but updating meson effect too many ports, I need this port merged first.

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

@dg0yt
Copy link
Contributor

dg0yt commented Mar 9, 2024

No. it takes 1.5 years of expert time to update port meson.
#28084

@vipcxj vipcxj changed the title [gstreamer] update to 1.3.2 [meson] update to 1.3.2 Mar 9, 2024
@vipcxj
Copy link
Contributor Author

vipcxj commented Mar 9, 2024

@dg0yt I think vcpkg should provide a mechanism to globally set the meson version to be used, and each port can individually specify the meson version it needs, so that when a port needs a higher version of meson, it only needs to add this version of meson and specify the port to use it, which won't affect any of the older port

@dg0yt
Copy link
Contributor

dg0yt commented Mar 9, 2024

@dg0yt I think vcpkg should provide a mechanism to globally set the meson version to be used, and each port can individually specify the meson version it needs, so that when a port needs a higher version of meson, it only needs to add this version of meson and specify the port to use it, which won't affect any of the older port

Don't tell me.
#31748 (comment)

@dg0yt
Copy link
Contributor

dg0yt commented Mar 9, 2024

I think you can close this PR.

@vipcxj vipcxj closed this Mar 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants