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

[libressl] Fix GitHub download URL #42218

Merged
merged 2 commits into from
Nov 19, 2024

Conversation

donny-dont
Copy link
Contributor

@donny-dont donny-dont commented Nov 18, 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.

The URL was missing the `$` in front of `{VERSION}`.

Remove warnings patch since its unnecessary.
@JonLiu1993 JonLiu1993 self-assigned this Nov 19, 2024
@JonLiu1993 JonLiu1993 added the category:port-bug The issue is with a library, which is something the port should already support label Nov 19, 2024
FILENAME "${PORT}-${VERSION}.tar.gz"
SHA512 b5ec6d1f4e3842ecb487f9a67d86db658d05cbe8cd3fcba61172affa8c65c5d0823aa244065a7233f06c669d04a5a36517c02a2d99d2f2da3c4df729ac243b37
)

vcpkg_download_distfile(WARNINGS_REMOVAL_PATCH
Copy link
Member

Choose a reason for hiding this comment

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

Can you explain why you removed this patch?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Sounded like @dg0yt wanted it removed but it was merged before I got to it.

see #42145 (review)

Copy link
Member

Choose a reason for hiding this comment

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

The patch isn't to fix some warning that fails under /WX?

If the warning just ends up in logs that nobody cares about, then sure, it has no real reason to be here, but I'm assuming if it went to a long forlorn and forgotten text file that someone wouldn't have taken the effort to backport it.

Copy link
Contributor Author

@donny-dont donny-dont Nov 19, 2024

Choose a reason for hiding this comment

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

Nope /WX is not present.

I’ve been running a vcpkg registry since 2018 at https://github.com/WebKitForWindows/WebKitRequirements for the Windows WebKit port. We’re getting outside contributors including your cohorts at https://playwright.dev/ . So I’m trying to migrate to the canonical registry.

Picked up the libressl port and tried to land the patches that were present here upstream. Was trying to be neighborly by doing that. Maybe in the past it was required 🤷 but it’s not anymore. And the patch will be present in the next release.

Can keep the patch or drop it. Don’t have a strong opinion

Copy link
Contributor

Choose a reason for hiding this comment

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

Maybe I didn't pay enough attention...
There might be users which bring custom toolchains that apply /WX.
So patches to resolve issues with /WX are useful.

Copy link
Member

Choose a reason for hiding this comment

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

Nah, we normally patch out /WX things, and we normally don't expect ports to be warning clean on all platforms, because port consumers generally can't do anything about the results.

If the patch is not needed for the port to build successfully and only affects logs, I agree with @dg0yt's original comment

@BillyONeal BillyONeal merged commit 0661551 into microsoft:master Nov 19, 2024
16 checks passed
@BillyONeal
Copy link
Member

Thanks for the fix!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category:port-bug The issue is with a library, which is something the port should already support
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants