-
Notifications
You must be signed in to change notification settings - Fork 10.4k
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
Simplify obtaining of swift sources #31
Simplify obtaining of swift sources #31
Conversation
@@ -0,0 +1,11 @@ | |||
#!/usr/env bash | |||
|
|||
git clone git@github.com:apple/swift.git swift |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If the Swift team goes ahead with this approach, please can #29 be changed here too.
+1 |
This may need to be taken into consideration as well. |
TY @stuarthannig Change has been made. |
Hmmm, that would require the installation of |
He's not recommending the use of |
👎 * 💯 No offense to @BrandonMathis, but folks who write documentation that tells users to curl pipe into bash need to stop writing documentation until they learn why that is a severe anti-pattern that needs to die. |
Agreed. If anything, couldn't |
Exactly. |
Yes a thousand times! There is nothing worse than seeing that in documentation. |
complicates maintenance, and less secure. |
Ah Thanks @jetpacmonkey & @jsjohnst that is a pretty good point. Running arbitrary code from a curl command would be very off-putting to many developers! I do like @davidcelis' suggestion of moving this functionality into |
I would prefer the VCS-related functionality to be separate from the build-script. The build script is being executed in automated environments, like CI and build machines, that need to reliably build a given source tree, so it shouldn't have the functionality to download sources from the network.
|
@BrandonMathis, you are on par with @AndreasPrang on commits quantity that you need to fix URL. |
Agreed, thx for the suggestion @gribozavr |
@Leandros It may make sense to actually provide a curlsh line to drive awareness, the script could be as simple as:
|
@gribozavr, Moved this into Thanks for the help all! Excited to see what the future of swift will hold. 📝 Merging this will also close: |
I'm not sure if
|
git clone git@github.com:apple/swift-corelibs-xctest.git | ||
git clone git@github.com:apple/swift-corelibs-foundation.git | ||
|
||
./utils/update-checkout --clone |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One still needs to clone the swift repo, and then cd
into it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
Great catches @gribozavr! |
@@ -52,6 +53,21 @@ def update_working_copy(repo_path): | |||
else: | |||
check_call([ "svn", "update" ]) | |||
|
|||
def obtain_additional_swift_sources(): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is outside the scope of what this script is meant for. This script updates current sources.. At this point you are getting into package management.. There are separate utils for this within swift.
很好很强大 |
@BrandonMathis Sorry, just noticed that the readme was updated to include both sets of instructions for both https and ssh access, and that your pull request changes it to use https only. There are trade-offs between https and ssh. HTTPS is friendlier for people who don't have a github account. Using ssh by default optimizes for the developers with commit access. Do you think we could also add a |
I suggest to leave ability to clone whole sources by the script behind some option like '--full' . One may want to simply download this script and execute it standalone. |
@@ -16,6 +16,7 @@ from __future__ import print_function | |||
import argparse | |||
import os | |||
import sys | |||
import pdb |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
pdb
needed? :-)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nope, nice catch :)
@gribozavr, support for cloaning via ssh has been added via a |
Simplify obtaining of swift sources
Thanks, @BrandonMathis! |
Can do @gottesmm 😬👍🏼 |
Cleanup test status
* [WASM] Disable mmap test case for WASI OS due to lack of WASI API * [WASM] Disable simd test case for WASI OS simd api maybe stable in future https://github.com/WebAssembly/simd * [WASM] Fix to build pthread pollyfill only when wasi sdk * [WASM] Implement parsing command line arguments * [WASM] Run StdlibUnittest in process instead of child proc
* [WASM] Disable mmap test case for WASI OS due to lack of WASI API * [WASM] Disable simd test case for WASI OS simd api maybe stable in future https://github.com/WebAssembly/simd * [WASM] Fix to build pthread pollyfill only when wasi sdk * [WASM] Implement parsing command line arguments * [WASM] Run StdlibUnittest in process instead of child proc
[pull] swiftwasm from apple:master
With hopes of making the install/obtaining of sources process easier. I have collapses all github repo clone commands into a
utils/clone_resources.sh
command which can be run via a curl command.Readme updated as well