Community Packages

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#67075 - [dotnet-sdk] Split NETStandard.Library.Ref from the dotnet-sdk package

Attached to Project: Community Packages
Opened by Florian Maunier (fmauNeko) - Monday, 22 June 2020, 12:42 GMT
Last edited by Maxime Gauduin (Alucryd) - Thursday, 30 July 2020, 17:14 GMT
Task Type Feature Request
Category Packages
Status Closed
Assigned To Maxime Gauduin (Alucryd)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No



I'm opening that task to propose that the NETStandard.Library.Ref subfolder (located in /usr/share/dotnet/packs/NETStandard.Library.Ref/<version>) is split from the main dotnet-sdk package, in order to allow for multiple versions of the SDK to depend on that common pack.

Indeed, .NET 5.0 previews also ships with those files, which prevents them from being installed side-by-side even though it definitely works.

I've worked around that by excluding this folder from dotnet-sdk-preview on AUR, and depending on dotnet-sdk-3.1, but I think splitting this subfolder would be the best course of action.
This task depends upon

Closed by  Maxime Gauduin (Alucryd)
Thursday, 30 July 2020, 17:14 GMT
Reason for closing:  Implemented
Additional comments about closing:  -> aspnet-runtime-3.1.6.sdk106-2-x86_64.pkg .tar.zst (x86_64)
-> aspnet-targeting-pack-3.1.6.sdk106-2-x86 _64.pkg.tar.zst (x86_64)
-> dotnet-host-3.1.6.sdk106-2-x86_64.pkg.ta r.zst (x86_64)
-> dotnet-runtime-3.1.6.sdk106-2-x86_64.pkg .tar.zst (x86_64)
-> dotnet-sdk-3.1.6.sdk106-2-x86_64.pkg.tar .zst (x86_64)
-> dotnet-targeting-pack-3.1.6.sdk106-2-x86 _64.pkg.tar.zst (x86_64)
-> netstandard-targeting-pack-3.1.6.sdk106- 2-x86_64.pkg.tar.zst (x86_64)
Comment by Maxime Gauduin (Alucryd) - Thursday, 30 July 2020, 13:23 GMT
Agreed, it seems to be how Microsoft ships their packages as well, will do that now that dotnet builds again.