Support .NET Core 2.1

[hansfn]

Looking at https://dotnet.microsoft.com/download/archives it seems we should support 2.1 (and 2.2) and drop support for 2.0. Are there are plans or stoppers for this?

I'm currently testing the 2.0.7 ebuild unmodified for 2.1.8 and will report back. (I'm only testing "dotnetcore-runtime-bin".)

PS! I also notice that the ebuilds for 2.0 is outdated. Current version is 2.0.9 and we have dotnetcore-aspnet-bin-2.0.3.ebuild and dotnetcore-runtime-bin-2.0.7.ebuild

[hansfn]

Just for the record: I have successfully installed "dotnetcore-runtime-bin" version 2.1.8 (and tested against one application) using an unmodified 2.0.7 ebuild. Since this is a trivial change, I haven't provide a PR but I'm happy to do so.

[ostroffjh]

I'm using 2.2.103 of dotnetcore-sdk-bin. I'm having trouble emerging some other dev-dotnet packages, but I do not believe dotnetcore is related. It seems the sdk packages are all 2.1 and 2.2, but the runtime ones are still 2.0. I suspect a PR for newer version is likely to be accepted.

[ostroffjh]

I'm also curious why dotnetcore-sdk-bin has 2.1 and 2.2 versions, but dotnetcore-sdk only has 1.x. I doubt I'm the first one to ask this, but I don't recall seeing any explanations.

[gsnerf]

If I recall correctly (but I might be wrong here) newer dotnetcore-sdk versions use dotnet itself to build at some point, which currently doesn't work in sandboxed enviroments like ebuild execution. The dotnet runtime will just hang without message: https://github.com/dotnet/coreclr/issues/17045

[ostroffjh]

There is work on being able to build without preexisting binaries - see https://github.com/dotnet/source-build. Discussion at https://gitter.im/dotnet/source-build. Tarballs are not sufficient to build, so you have to clone first. I'm working my way through it now.