Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Install the SwiftPM/Swift Build resources in /usr/share/pm #418

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

owenv
Copy link

@owenv owenv commented May 6, 2025

Builds on #417 - only the second commit is new

Ensure the Windows installer includes the resources bundled in swiftlang/swift-build#488

Copy link
Member

@compnerd compnerd left a comment

Choose a reason for hiding this comment

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

I'd rather that we explicitly list the files if possible. Do you expect the list to constantly change dramatically? The only place that we currently harvest is in the clang resources, which has continued to be a source of installation failures. I think that we should prefer to just enumerate the content that we are distributing.

@owenv
Copy link
Author

owenv commented May 6, 2025

I don't expect the list to change dramatically, but it is added to fairly often, and it's unfortunate if we have to stage cross-repo changes every time that happens

@owenv owenv force-pushed the owenv/swift-build-resources branch from 7db0a42 to 4b174e0 Compare May 8, 2025 04:15
@owenv owenv changed the title Harvest the SwiftPM/Swift Build resources in /usr/share/pm Install the SwiftPM/Swift Build resources in /usr/share/pm May 8, 2025
@owenv
Copy link
Author

owenv commented May 8, 2025

I updated this patch to explicitly list everything and am autogenerating the content via scripts in the Swift Build repo

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