Determine how to build portable assets for N when N-1 didn't build portable assets.
Open
area-doc
- Dominant language
- No language data
- Stars
- 287
- Forks
- 145
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 10
Description
On Fedora, .NET Core 3.1 was bootstrapped without building portable assets (that source-build feature wasn't merged yet). Now, it fails to build portable bits because it requires portable prereqs from previously-source-built.
How can a distro maintainer bridge this gap? Can we use non-portable assets to build portable assets?
Or does a "build chain" that bootstrapped without portable builds always need to pass `/p:SkipPortableRuntimeBuild=true`?
Context starting here in Gitter: https://gitter.im/dotnet/source-build?at=5e6ab35f06898177494ab964
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.