Description
With new packaging infra (PR #45047) we are producing packages that have some minor differences in metadata content - fields and dependency info.
Most of these should be fine as the values now match what we've used in runtime
packages in the past.
DEB
old infra | new infra | |
---|---|---|
Version | 10.0.100-alpha.1.24568.3-1 | 10.0.100~alpha.1.24568.3 |
Maintainer | Microsoft dotnetcore@microsoft.com | .NET Team dotnetpackages@dotnetfoundation.org |
Installed-size | 367966 | 374217022 |
Section | devel | libs |
Section
field is different - I am unsure of the significance of this. The value is hard-coded at https://github.com/dotnet/arcade/blob/2a3bf4e3a4c473135d058adcd7193a5a4bcd38a7/src/Microsoft.DotNet.Build.Tasks.Installers/build/installer.build.targets#L253
RPM
Dependencies
old infra | new infra | |
---|---|---|
New dependency | rpmlib(TildeInVersions) <= 4.10.0-1 | |
Old dependency | aspnetcore-runtime-10.0 | aspnetcore-runtime-10.0 >= 10.0.0~alpha.2.24526.1 |
Old dependency | aspnetcore-targeting-pack-10.0 | aspnetcore-targeting-pack-10.0 >= 10.0.0~alpha.2.24526.1 |
Old dependency | dotnet-apphost-pack-10.0 | dotnet-apphost-pack-10.0 >= 10.0.0~alpha.1.24527.3 |
Old dependency | dotnet-runtime-10.0 | dotnet-runtime-10.0 >= 10.0.0~alpha.1.24527.3 |
Old dependency | dotnet-targeting-pack-10.0 | dotnet-targeting-pack-10.0 >= 10.0.0~alpha.1.24527.3 |
DEB packages had specific version for dependencies, even in old infra, so this update for RPM seems like a good idea, and it also matches what runtime RPMs always had.
Metadata
old infra | new infra | |
---|---|---|
Version | 10.0.100_alpha.1.24528.3 | 10.0.100 |
Release | 1 | 0.1.alpha.1.24528.3 |
License | MIT | MIT and ASL 2.0 and BSD |
Packager | Microsoft dotnetcore@microsoft.com | .NET Team dotnetpackages@dotnetfoundation.org |
Version, Release, License and Packager fields now match what we had in runtime packages (built with old or new infra).