-
Notifications
You must be signed in to change notification settings - Fork 353
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
Phase1 doc for native bootstrapping #129
Conversation
|
||
## Scope | ||
|
||
- Pre-CLI toolsets |
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
|
||
- Pre-CLI toolsets | ||
|
||
- Xcopy deployable native dependencies |
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
|
||
- Create zips / tarballs of a couple of xcopy deployable native dependencies (like cmake) which are stored and publically accessible in Azure blob storage. These will be proof of concept, and not an exhaustive list of native toolset dependencies. | ||
|
||
- Determine how repos will define a dependency version list for native dependencies which fits into the [dependency description](https://github.com/dotnet/arcade/pull/120/files) spec or modifies it where necessary |
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
I have some additional questions that aren't covered in the doc:
|
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.
Looks good overall but probably needs some extra detail in some areas
Thanks Matt, this doc is a high-level overview and, you're right, it's light on details. More details are in the referenced issue #131. |
|
||
- Determine how repos will define a dependency version list for native dependencies which fits into the [dependency description](https://github.com/dotnet/arcade/pull/120/files) spec or modifies it where necessary | ||
|
||
- Create [Powershell](https://docs.microsoft.com/en-us/powershell/scripting/setup/installing-windows-powershell?view=powershell-6) and bash scripts (these are in-box available tools) which are capable of understanding the dependency list and downloading / extracting versioned dependencies so that they are available in the repo from a well-known (or defined) location. |
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
|
||
- dependencies distributed as Nupkg's - Why not use nupkg's as the distribution mechanism? Nupkg's have a couple of desirable attributes including being versioned, tfm / runtime awareness, well-known format. There are a couple of downsides though. | ||
|
||
- All implementations of the dependency are packaged into a single unit. ie, you can't just download the Windows dependency from the package unless you package it separately. You would always bring down the Windows, Linux variants, and OSX implementations for a native dependency. |
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
|
||
- Non-Xcopy deployable dependencies | ||
|
||
- ie, docker, [Visual Studio](https://github.com/dotnet/arcade/issues/64), NodeJS, etc... |
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
We seem to have general agreement on native toolset bootstrapping phase1. Further discussions should occur in #131. I'll be updating that doc on 5/2 with the latest design changes. |
Fixes #122
/cc @markwilkie