source-build: bundle runtime packs with the sdk.#16499
source-build: bundle runtime packs with the sdk.#16499MichaelSimons merged 6 commits intodotnet:mainfrom
Conversation
|
Tested on my machine: 🎉 It would be nice to have an argument - similar to Alternatively, one can already add: <RuntimeIdentifier>$(NETCoreSdkRuntimeIdentifier)</RuntimeIdentifier>Using That leaves these two unique files in the .NET Core runtime pack: And these two unique files in the ASP.NET Core runtime pack: So we get source-build self-contained at the small cost of 4.2MB in size (provided the repo packages support hard links). |
7e3b49c to
d29c9b8
Compare
d29c9b8 to
243d157
Compare
|
I've added a property ( When turned on, we'll try to call Because the tool may not be available on every distro, I'll look into replacing the |
|
@ashnaga @MichaelSimons can this still be part or preview5? |
| </BundledLayoutPackage> | ||
|
|
||
| <BundledLayoutPackage Include="MicrosoftNetCoreAppRuntimePackNupkg" Condition="'$(BundleRuntimePacks)' == 'true'"> | ||
| <PackageName>Microsoft.NETCore.App.Runtime.$(SharedFrameworkRid)</PackageName> |
There was a problem hiding this comment.
Is SharedFrameworkRid the same as ProductMonikerRid? ProductMonikerRid is used earlier for the known framework reference RIDs.
There was a problem hiding this comment.
I'm using the same parameters as we were are already using for the app host, and they are both equal to the non-portable rid.
Co-authored-by: Daniel Plaisted <dsplaisted@gmail.com>
|
@tmds - Can you log a follow-up test to ensure we adjust the source-build tests run a self-contained scenario and verify the runtime pack doesn't get pulled from NuGet? The change @mthalman is making in #16359 should make this a lot easier.
I am going to defer this to @marcpopMSFT and @dsplaisted since this is an installer product change. |
Created dotnet/source-build#3485. |
@MichaelSimons what is the best place to put this Task? Is it https://github.com/dotnet/installer/tree/main/src/core-sdk-tasks? Or does it belong somewhere else? |
I will defer to @dsplaisted. |
|
Per today's tactics meeting, we are at the point in the release cycle that only critical fixes are being accepted for preview 5. It sounds like this will have to be deferred to preview 6. cc @mmitche for visibility. |
Contributes to dotnet/source-build#1215.
@dsplaisted @MichaelSimons ptal.
cc @ashnaga @omajid @uweigand