3 ms·
While there aren't necessarily native packages pre-built and ready to pull down with the installers, you don't need to be a 'software packager' to install .NET
by rikkus 10y ago
While there aren't necessarily native packages pre-built and ready to pull down with the installers, you don't need to be a 'software packager' to install .NET Core and I don't know what the problem is with 'add[ing] a separate PPA'
Instructions for Debian[1], Fedora[2], Centos[3] and Ubuntu[4]. These all seem like pretty simple copy+paste instructions.
[1] https://www.microsoft.com/net/core#linuxdebian https://www.microsoft.com/net/core#linuxdebian
[2] https://www.microsoft.com/net/core#linuxfedora https://www.microsoft.com/net/core#linuxfedora
[3] https://www.microsoft.com/net/core#linuxcentos https://www.microsoft.com/net/core#linuxcentos
[4] https://www.microsoft.com/net/core#linuxubuntu https://www.microsoft.com/net/core#linuxubuntu
- cryptarch 10y agoI don't want 3rd party repositories to manage. To do it properly I have to (in the case of Debian) trust some MS team's signing keys (yuck), add the repo and update my apt-pinning rules (I don't want apt accidentally installing MS versions of tools) and integrate this in my dev OS build automation. That vs. adding a single line in my list of selected packages. The price to adoption is high and it's just not worth it to me, especially seeing how immature the tooling and overall ecosystem is.