As stated more ebuilds relating to dotnet, if possible to be merged into the main portage tree to expand the dev-dotnet package group, such as msbuild,fsharp,rosyln, and others to expand the usability of portage to make implenting such programs into portage easier (those that rely on msbuild especially)
Why? Could you please explain how usable would they be when we have all that in dotnet-SDK now?
(In reply to Maciej Barć from comment #1) > Why? Could you please explain how usable would they be when we have all that > in dotnet-SDK now? My bad did not see this in terms of the dotnet-sdk, thanks for making me aware of this Maciej! Also very happy to see the dotnet-sdk ebuild finally and not just dotnet-sdk-bin
(In reply to Kyle Rabago from comment #2) > (In reply to Maciej Barć from comment #1) > > Why? Could you please explain how usable would they be when we have all that > > in dotnet-SDK now? > > My bad did not see this in terms of the dotnet-sdk, thanks for making me > aware of this Maciej! Also very happy to see the dotnet-sdk ebuild finally > and not just dotnet-sdk-bin Both of them have those tools available. Currently 7.0 and 8.0 SDKs can be installed from-source.
(In reply to Maciej Barć from comment #3) > (In reply to Kyle Rabago from comment #2) > > (In reply to Maciej Barć from comment #1) > > > Why? Could you please explain how usable would they be when we have all that > > > in dotnet-SDK now? > > > > My bad did not see this in terms of the dotnet-sdk, thanks for making me > > aware of this Maciej! Also very happy to see the dotnet-sdk ebuild finally > > and not just dotnet-sdk-bin > > Both of them have those tools available. Currently 7.0 and 8.0 SDKs can be > installed from-source. Thanks!