Skip to content

Swiftly proxies for tools in the toolchain #150

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

Closed
cmcgee1024 opened this issue Aug 6, 2024 · 1 comment
Closed

Swiftly proxies for tools in the toolchain #150

cmcgee1024 opened this issue Aug 6, 2024 · 1 comment
Assignees
Labels
release candidate This issue is a candidate for the next release

Comments

@cmcgee1024
Copy link
Member

Swiftly can use proxy executables for tools in the toolchain instead of symlinks. The proxies can decide their targets at invocation time in this way instead of at swiftly use time, for greater configurability. For example, the proxies can respond to special parameters among the typical tool arguments like this:

swift build +main-snapshot # build with the latest available snapshot

This feature would not be possible with symlinks since they cannot respond to the arguments.

Also, proxies can make use of the .swift-version files that are popular in some Swift repositories to align the team on a single language and toolchain version. If no version is specified using the special command-line parameter then the proxies can search for a version file in the current working directory, or an ancestor, to automatically install and use the correct toolchain for the project on every tool invocation, such as after a git pull.

@cmcgee1024 cmcgee1024 added the release candidate This issue is a candidate for the next release label Aug 6, 2024
@cmcgee1024 cmcgee1024 self-assigned this Sep 12, 2024
@cmcgee1024
Copy link
Member Author

This is finished in #155

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release candidate This issue is a candidate for the next release
Projects
None yet
Development

No branches or pull requests

1 participant