FS#59195 - [dotnet-runtime] messes with Runtime Identifier (RID)
Attached to Project:
Community Packages
Opened by morguldir (morguldir) - Saturday, 30 June 2018, 23:58 GMT
Last edited by Maxime Gauduin (Alucryd) - Monday, 01 October 2018, 11:14 GMT
Opened by morguldir (morguldir) - Saturday, 30 June 2018, 23:58 GMT
Last edited by Maxime Gauduin (Alucryd) - Monday, 01 October 2018, 11:14 GMT
|
Details
[dotnet-core] 2.1.1+301-1 The dotnet packages are adding
their own Runtime Identifiers, RID's are used to identify
the operating system that it is running on so that you can
target libraries to that platform, the package maintainer
has decided to add their own RID which breaks this
functionality for arch users.
The intended way the shell scripts should work is that they set __PortableBuild to 1 for unsupported versions, and then change the version to just linux-$arch if the variable is set to 1, however, if you look at the patch that adds arch, it adds an if statement right before it sets the portable build variable. https://git.archlinux.org/svntogit/community.git/tree/trunk/dotnet-coreclr-rid.patch?h=packages/dotnet-core This is a change that should be made upstream so that having arch as an RID can be translated into linux. https://docs.microsoft.com/en-us/dotnet/core/rid-catalog Affected packages: dotnet-runtime 2.1.1+301-1 dotnet-host 2.1.1+301-1 dotnet-sdk 2.1.1+301-1 aspnet-runtime 2.1.1+301-1 |
This task depends upon
Comment by
Maxime Gauduin (Alucryd) -
Thursday, 05 July 2018, 09:22 GMT
And if you look even closer at the patch you realize that this is
only for the build-test.sh script, which isn't even used, the
package is built using the build.sh script, which doesn't mess
with portable build. Also, arch-$arch was automatically chosen by
other parts of the runtime, it's only logical to keep it for
coreclr as well...