Chris McGee

Results 45 issues of Chris McGee

Sometimes the target's name and rule kind don't provide much detail on its purpose. When should the target be used? Is it runnable, testable, or just buildable? Maybe it's meant...

type: feature request
P4

Use SwiftPM to compile and link in libarchive using a vendored version of it. This will help to ensure that it is statically linked into the final binary in both...

See issue #149 Using the new swift.org API is more accurate than the GitHub API, also it isn't subject to the same rate limits. Use the swift.org API instead of...

Add a design for the new swiftly proxy system for more flexible routing of command invocations to a toolchain. Re-target the symbolic links that swiftly creates to point to swiftly...

There are some comments in the code about using swift.org metadata about toolchain versions in toolchain search and selection instead of the GitHub API's. This would reduce the site dependencies...

release candidate

Swiftly currently only support Linux and macOS. It could support the Windows platform too.

The current script for building a release assumes that the only artifacts will be single static binaries, and at the moment it's only making Linux binaries for the supported architectures...

release candidate

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

release candidate

Currently, CI only runs pull requests when they are opened, changed, or someone asks using a comment on a PR. There should be a post-merge CI for swiftly that checks...

release candidate

Change SwiftlyVersion to make it more conformant to the semantic version specification (https://semver.org) with respect to pre releases. Add test cases that cover typical scenarios. Update the swiftly version to...